[Script] WME Toolbox (>1.4.2.8)

[iainhouse]

@OyyoDams

1.4.3.1
New: Force arrows to be selectable after loading (avoid noobs complaining about disabled arrows)

I understand why you’ve done this - particularly given the number of editors who have complained about Toolbox disabling arrows when it’s their own ignorance. :roll: At least it’s a testament to how many editors now rely on Toolbox.

However, it’s driving me crazy! :lol:

Any chance of a checkbox in the options to stop this behaviour?

[Arnoniem]

@OyyoDams

Can you make a better permalink ? No segment seems to be selected when I click on your link…Thanks

:oops: I must have changed the segment ID’s after I made the link. sorry. here it is again: https://www.waze.com/editor/?zoom=6&lat=25.29685&lon=55.43877&layers=1413&env=row&segments=255442080,255286467

The 2 ramps are creating a “same connection” which I can continuously repair with suppress… then autofix loop.

[OyyoDams]

@iainhouse

@OyyoDams

1.4.3.1
New: Force arrows to be selectable after loading (avoid noobs complaining about disabled arrows)

I understand why you’ve done this - particularly given the number of editors who have complained about Toolbox disabling arrows when it’s their own ignorance. :roll: At least it’s a testament to how many editors now rely on Toolbox.

However, it’s driving me crazy! :lol:

Any chance of a checkbox in the options to stop this behaviour?

OK I’ll add an option for L3 and more. It’ll be forced for noobs

[OyyoDams]

@Arnoniem

@OyyoDams

Can you make a better permalink ? No segment seems to be selected when I click on your link…Thanks

:oops: I must have changed the segment ID’s after I made the link. sorry. here it is again: https://www.waze.com/editor/?zoom=6&lat=25.29685&lon=55.43877&layers=1413&env=row&segments=255442080,255286467

The 2 ramps are creating a “same connection” which I can continuously repair with suppress… then autofix loop.

Reproduced! It’ll be fixed in next release.

[OyyoDams]

1.4.3.2 New: Toolbox features displayed in toolbar can be disabled in configuration panel New: Highlight segments/nodes with expired restrictions in red New: [L3] Delete expired restrictions (past ending date) on screen Update: Force arrows to be selectable after loading - can be disabled in configuration panel starting from L3 editors Fix: [L3] Suppress unneeded junctions: bug in some complicated situations

[PesachZ]

@OyyoDams

1.4.3.2... New: Highlight segments/nodes with time restrictions in red if old restrictions have to be deleted New: [L3] Delete past restrictions (with gone ending date) on screen ...

I think the term you are looking for is “expired (partial) restrictions”.

New: Highlight segments/nodes with expired (partial) restrictions in red if expired restrictions have to be deleted New: [L3] Delete expired (partial) restrictions (past ending date) on screen

Sent using Tapatalk for Android 4.4.2

[Arnoniem]

@OyyoDams

1.4.3.2 New: Toolbox features displayed in toolbar can be disabled in configuration panel New: Highlight segments/nodes with expired restrictions in red New: [L3] Delete expired restrictions (past ending date) on screen Update: Force arrows to be selectable after loading - can be disabled in configuration panel starting from L3 editors Fix: [L3] Suppress unneeded junctions: bug in some complicated situations

All working fine. Thanks!

Can you figure why nodes A and B of this segment are not suppressed?

[russblau]

Firefox 30.0 won’t update Toolbox to v. 1.4.3.2; I right-click on the “WME Toolbox 1.4.3.1” line on the Extensions screen, click “Find Updates”, and nothing happens.

[OyyoDams]

@russblau

Firefox 30.0 won’t update Toolbox to v. 1.4.3.2; I right-click on the “WME Toolbox 1.4.3.1” line on the Extensions screen, click “Find Updates”, and nothing happens.

Strange, I’ve just tested on another computer and Toolbox update worked sucessfully.

[russblau]

@OyyoDams

@russblau

Firefox 30.0 won’t update Toolbox to v. 1.4.3.2; I right-click on the “WME Toolbox 1.4.3.1” line on the Extensions screen, click “Find Updates”, and nothing happens.

Strange, I’ve just tested on another computer and Toolbox update worked sucessfully.

Thanks, I tried it again and this time it worked.

By the way, I can’t get “copy segment attributes” to work. I figured out the interface and got to the dialog box, but when I click the “Copy” button, nothing happens.

[OyyoDams]

@russblau

By the way, I can’t get “copy segment attributes” to work. I figured out the interface and got to the dialog box, but when I click the “Copy” button, nothing happens.

I think I found the bug. I’ll publish a release tomorrow.

[OyyoDams]

1.4.3.3 Fix: bug in "Copy segment attributes"

[Arnoniem]

1. thanks, the copying works now, on latest update

2. I got this message, trying to clear road geometry: WME Toolbox: please report this error: ReferenceError: Enable_WMETB_Clear_Road_GeometryX is not defined
   It was on this segment: https://www.waze.com/editor/?zoom=6&lat=52.20063&lon=5.93077&layers=1925&segments=146389328&env=row

3. This morning, before the update, I couldn’t split this road. Now, I got the message, trying to split this same road:
   WME Toolbox: please report this error: TypeError: Cannot read property ‘length’ of null

4. Last comment or improvement suggestion: I always run into a lot of dead end roads, marked by validator, with either a soft turn at the end (enabled or disabled) or an enabled hard turn. Seeing the latest possibilities, on fixing all the loops or expired restrictions on the screen, rather than selecting one by one, i’d wanted to ask you, if you can implement the fix that is done (by JNF) on the dead end street with a soft turn, for the entire screen. Probably an L5 option? See this area for example, where it needs already 25+ fixes on a single screen.

[porubcan]

I’ve faced the error: WME Toolbox: please report this error: ReferenceError: Enable_WMETB_Clear_Road_GeometryX is not defined
too. permalink to area with many simple segments: https://www.waze.com/editor/?zoom=4&lat=48.28432&lon=18.13542&mapUpdateRequest=3302611&env=row&layers=2021

[OyyoDams]

1.4.3.4 Fix: bug in "Clear road geometry"

[kentsmith9]

@Arnoniem

4. Last comment or improvement suggestion: I always run into a lot of dead end roads, marked by validator, with either a soft turn at the end (enabled or disabled) or an enabled hard turn. Seeing the latest possibilities, on fixing all the loops or expired restrictions on the screen, rather than selecting one by one, i’d wanted to ask you, if you can implement the fix that is done (by JNF) on the dead end street with a soft turn, for the entire screen. Probably an L5 option? See this area for example, where it needs already 25+ fixes on a single screen.

I completely agree with this thought. Not sure if there is a downside to doing something like this, but it would sure be much more efficient with our limited time. Like restrict the operation to 150 so you don’t end up with too many saves pending.

[OyyoDams]

@Arnoniem

3. This morning, before the update, I couldn’t split this road. Now, I got the message, trying to split this same road:
   WME Toolbox: please report this error: TypeError: Cannot read property ‘length’ of null

Will be fixed in next release.

[OyyoDams]

@Arnoniem

4. Last comment or improvement suggestion: I always run into a lot of dead end roads, marked by validator, with either a soft turn at the end (enabled or disabled) or an enabled hard turn. Seeing the latest possibilities, on fixing all the loops or expired restrictions on the screen, rather than selecting one by one, i’d wanted to ask you, if you can implement the fix that is done (by JNF) on the dead end street with a soft turn, for the entire screen. Probably an L5 option? See this area for example, where it needs already 25+ fixes on a single screen.

I think I understand, and that’s technically possible. Just to be sure, in the case of an unconfirmed dead-end, how do you think we should handle it ? Mark it as enabled or disabled ? I think it should be disabled, but I’d like to have other thoughts.

[kentsmith9]

@OyyoDams

I think I understand, and that’s technically possible. Just to be sure, in the case of an unconfirmed dead-end, how do you think we should handle it ? Mark it as enabled or disabled ? I think it should be disabled, but I’d like to have other thoughts.

Disabled is the current operation of JNF. I believe we know of routing problems when it is enabled, so that would be bad.

[glomp]

I get the “WME Toolbox: please report this error: TypeError: this is undefined” after the latest update to v1.4.3.4

FF v31, OS X v10.9.3