Page 2 of 12

Re: [Script] WME Closest Segment

Posted: Sun Jan 29, 2017 11:14 pm
by G_W1Z
JustinS83 wrote:
jwe252 wrote:Cannot delete a place with this script enabled since the update.
Sorry about that!

Updated released - version 1.0.2.4
Bug fix - could not delete Places after the previous update.
Thanks for releasing these updates! I can save with the new release but it isn't showing the line from the PP to the nearest road.

Re: [Script] WME Closest Segment

Posted: Tue Jan 31, 2017 7:07 pm
by G_W1Z
JustinS83 wrote:
I haven't had any issue with the line not showing. Please check your console for errors.
Works now. Thanks!

Re: [Script] WME Closest Segment

Posted: Thu Jul 13, 2017 6:51 pm
by G_W1Z
This script disrupts edits for AP's.

Example: I go to edit a school AP. I make 3-4 edits. These edits do not show next to the save disk icon. If I go and edit anything else except an AP (such as a road or a PP) the count reappears and includes my edits from the AP. Until I do something like that I cannot save my edits to the AP, even with Ctrl+S.

Re: [Script] WME Closest Segment

Posted: Thu Jul 13, 2017 7:02 pm
by G_W1Z
dspille wrote:
G_W1Z wrote:This script disrupts edits for AP's.
Have you considered using WME PIE, which has now incorporated the CS functionality (and improved upon it)?
I have PIE installed and use it. I just wanted to pass along my experience in case it was considered a bug worth squashing.

Re: [Script] WME Closest Segment

Posted: Thu Mar 02, 2017 4:30 pm
by gOyDp
New bug. The script doesn't work for me.

Chrome v56

I get this error.

Code: Select all

Uncaught TypeError: Cannot read property 'venue' of null
    at e.checkSelection (eval at <anonymous> (:2:297), <anonymous>:1440:39)
    at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:101:6363)
    at e.value (https://www.waze.com/assets-editor/js/app-fc5fff5290109f2cacdf.js:11:23912)
    at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:101:6363)
    at initialize.select (https://www.waze.com/assets-editor/js/app-fc5fff5290109f2cacdf.js:14:20814)
    at initialize.clickFeature (https://www.waze.com/assets-editor/js/app-fc5fff5290109f2cacdf.js:14:18782)
    at initialize.callback (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:102:27046)
    at initialize.triggerCallback (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:103:8483)
    at initialize.handle (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:103:8008)
    at initialize.click (https://www.waze.com/assets-editor/js/vendor-1747fc375941d3abdd6d.js:103:7119)
checkSelection @ VM3387:1440
triggerEvent @ vendor-1747fc3….js:101
value @ app-fc5fff5….js:11
triggerEvent @ vendor-1747fc3….js:101
select @ app-fc5fff5….js:14
clickFeature @ app-fc5fff5….js:14
callback @ vendor-1747fc3….js:102
triggerCallback @ vendor-1747fc3….js:103
handle @ vendor-1747fc3….js:103
click @ vendor-1747fc3….js:103
triggerEvent @ vendor-1747fc3….js:101
handleBrowserEvent @ vendor-1747fc3….js:101
(anonymous) @ vendor-1747fc3….js:99
Further digging shows this exception:

Code: Select all

function checkSelection() {
		'use strict';
		log('Selection change called.', 2);

		navPoint = W.geometryEditing.editors.venue.navigationPoint; **** This where the exception is being caught. 
...
Any ideas on resolution?

Re: [Script] WME Closest Segment

Posted: Thu Mar 02, 2017 6:21 pm
by gOyDp
That was the actual problem. Someone should update the URL.

The one at the top of this thread and when you search Google takes you to the incorrect version.

Re: [Script] WME Closest Segment

Posted: Tue Jul 19, 2016 6:46 am
by james890526
Any plans to update the link for WME beta? While changes can be done individually, I figure it's better for the script author to update the script too?

Re: [Script] WME Closest Segment

Posted: Sun Jun 19, 2016 10:04 pm
by jjczon
Did it stop working again after the recent WME changes?

Re: [Script] WME Closest Segment

Posted: Tue May 23, 2017 9:19 pm
by jm6087
Ahh, that was my problem as well. Thanks for the update. Very nice

Re: [Script] WME Closest Segment

Posted: Fri May 26, 2017 9:40 am
by juliansean
Thank you for updating this so quickly!