[Script] WME Toolbox

[n4dog]

@BellHouse

@n4dog

By the way no longer able to select a segment and Hit “1” to clear the geometry.

Maybe you’ve lost the key binding? What does your keyboard shortcuts entry “Clear road geometry” (in “Toolbox” section) say?

It is there and visible. Just was easier to hit the #1.

[BellHouse]

@n4dog

@BellHouse

@n4dog

By the way no longer able to select a segment and Hit “1” to clear the geometry.

Maybe you’ve lost the key binding? What does your keyboard shortcuts entry “Clear road geometry” (in “Toolbox” section) say?

It is there and visible. Just was easier to hit the #1.

Sorry, I don’t get it. You can bind the function to any key you want, be it “1”, “[NumPad]1” or whatever else. :?

[n4dog]

@BellHouse

quote]
Sorry, I don’t get it. You can bind the function to any key you want, be it “1”, “[NumPad]1” or whatever else. :?

Mine has always worked? Never did any binding of any kind. Would not even know how. I would just select the segment and press the number 1 key and it would clear the segment

[valginhak]

I was not able to set the 1 key to clear segments. In the configuration panel everything was “NONE”, and it did not accept to configure. After going to “Reset WME Toolbox Settings”, the settings have responded again. Hope you understand my English (by GT), and help you set up.

[BellHouse]

I just became aware that in the current release 1.7.4 there are indeed no default key bindings (by accident). We had noticed this some days ago and have already adjusted this in our development version, but this has not been released yet. So in release 1.7.5 you will again find the default key bindings as previously, such as binding the key “1” to the function “clear road geometry”. Sorry for the confusion.

[BellHouse]

Toolbox 1.7.5 is released for Chrome and Firefox:

1.7.5 (20170220) New: Selecting a parking lot (PL) venue displays a popup with the PL type (#374) Fix: Default keyboard shortcuts were not initialized correctly (#371) Fix: Lock highlights visibility was not initialized correctly after Toolbox reset (#372) Fix: Measurement tool window covered zoombar (#373) Fix: Visibility settings of parking lot and residential place layers were cut off by permalink auto-repair (#375) Fix: Internal JNF failed to repair dead-end (1 segment) loops (#376) Fix: Convert roundabout to standard road failed on 1 segment roundabout loops (#377) Update: Auto fix loops function now also repairs (dead end) 1 segment loops (#378) Update: Support for modified permalink format in WME beta (#379) Update: Categorized popups in infos (green border) and warnings (red border)

[valginhak]

@BellHouse

I just became aware that in the current release 1.7.4 there are indeed no default key bindings (by accident). We had noticed this some days ago and have already adjusted this in our development version, but this has not been released yet. So in release 1.7.5 you will again find the default key bindings as previously, such as binding the key “1” to the function “clear road geometry”. Sorry for the confusion.

Now in version 1.7.5, some keys are already set by default. Thanks for keeping Toolbox updated, without it our work would be very difficult.

[RussPA]

@lg1992

I use WME KeepMyLayers, so all permalinks that I use don’t include the “layers” part. I’ve noticed that if I do some editing, save my work, and then reload the same page, I often loose selection of the layers “Residential” and “Parking lots”. After some investigation I’ve found that it only happens when WME Toolbox is enabled.

The problem only happens in WME beta and never in production. It doesn’t happen if disable all scripts besides the WME Toolbox and then load a permalink with the “layers” part, but without the “layers” part it reproduced intermittently.

I noticed something similar to this. If I use the Toolbox button to switch between beta/prod, when I switch to beta, the layers always revert to this: Map & Place Issues, Venues, Junction Box, Closures, Speed Cameras, Map Comments, Area Managers, GPS Points, Editable Areas turn on and everything else turns off. It doesn’t matter how I had the layers set previously, it always defaults to these. Switching to Prod doesn’t affect the prod layer settings, only switching to beta. I tried this with Tampermonkey disabled and only Toolbox active. This is with TB 1.7.5.

[BellHouse]

@RussPA

I noticed something similar to this. If I use the Toolbox button to switch between beta/prod, when I switch to beta, the layers always revert to this: Map & Place Issues, Venues, Junction Box, Closures, Speed Cameras, Map Comments, Area Managers, GPS Points, Editable Areas turn on and everything else turns off. It doesn’t matter how I had the layers set previously, it always defaults to these. Switching to Prod doesn’t affect the prod layer settings, only switching to beta. I tried this with Tampermonkey disabled and only Toolbox active. This is with TB 1.7.5.

Confirmed and logged in as issue #380. We’ll squash this bug, too.

[RussPA]

Toolbox also does not seem to always remember the last 5 settings below the toolbar configuration settings, like the “Convert permalinks to production WME” setting (which always turns off when switching to beta).

[dchary2418]

@n4dog

By the way no longer able to select a segment and Hit “1” to clear the geometry.

I can’t disallow all turns using the Q key (the button still works, also W works)
and Q works if you keep the node selected after pressing W

Dave

[BellHouse]

@dchary2418

I can’t disallow all turns using the Q key (the button still works, also W works)
and Q works if you keep the node selected after pressing W

https://www.waze.com/forum/viewtopic.php?f=819&t=145570&p=1314713#p1312762

[BellHouse]

@RussPA

Toolbox also does not seem to always remember the last 5 settings below the toolbar configuration settings, like the “Convert permalinks to production WME” setting (which always turns off when switching to beta).

I can duplicate setting “Convert permalinks to production WME” getting lost. Which other 4 are you referring to?

[RussPA]

Sorry, I tested some more and it’s just that one setting that doesn’t hold.

[n4dog]

The “1” key is working again. Thanks

[vaindil]

Due to a change by Mozilla, we had to convert the add-on to a new format. Most people won’t see any difference, it’s purely a change on the back-end. The main problem is that we can only support FF 45 and up. This will be the case as of 1.7.6 when it releases. We may hold off on doing this, that’s still TBD, but just a warning for those of you still on older versions.

[jm6087]

@BellHouse

@RussPA

Toolbox also does not seem to always remember the last 5 settings below the toolbar configuration settings, like the “Convert permalinks to production WME” setting (which always turns off when switching to beta).

I can duplicate setting “Convert permalinks to production WME” getting lost. Which other 4 are you referring to?

I have noticed the same issue. Additionally, the checkbox is lost on a hard refresh of WME Beta as well.

[bz2012]

Something seems to be dragging today:

[Violation] Long running JavaScript task took 1140ms
[Violation] Handler took 222ms of runtime (50ms allowed)
[Violation] Long running JavaScript task took 222ms
vendor.legacy-c757b70c4c0ba2fdcfc239c49f2ef6c627abcfda20cc8eb45e2837d4270827cf.js:4 [Violation] Handler took 362ms of runtime (150ms allowed)
[Violation] Forced reflow while executing JavaScript took 73ms
[Violation] Long running JavaScript task took 363ms
[Violation] Long running JavaScript task took 404ms
[Violation] Long running JavaScript task took 200ms
WME_Toolbox.prod.min.js:246 [Violation] Handler took 5473ms of runtime (50ms allowed)
[Violation] Long running JavaScript task took 5474ms
[Violation] Long running JavaScript task took 237ms
vendor.legacy-c757b70c4c0ba2fdcfc239c49f2ef6c627abcfda20cc8eb45e2837d4270827cf.js:4 [Violation] Handler took 643ms of runtime (150ms allowed)
[Violation] Long running JavaScript task took 645ms
[Violation] Handler took 100ms of runtime (50ms allowed)
[Violation] Handler took 291ms of runtime (50ms allowed)
[Violation] Long running JavaScript task took 291ms

Toolbox seems to be slowing things down. Making streetview practically unusable, and making editing generally ssslllooowww.

However, even with Toolbox disabled (that does speed things up a bunch!) there are still problems.

But with all else disabled, TB still has problems:

METB: Loading FP.
WME_Toolbox.prod.min.js:5 WMETB: waiting for FP…
WME_Toolbox.prod.min.js:5 WMETB: Loading DataTables.
WME_Toolbox.prod.min.js:5 WMETB: DataTables loaded.
WME_Toolbox.prod.min.js:851 WMETB: Initializing main features
WME_Toolbox.prod.min.js:866 WMETB: loading saved options
WME_Toolbox.prod.min.js:5 WMETB: waiting for standalone JNF…
WME_Toolbox.prod.min.js:5 WMETB: using internal JNF
WME_Toolbox.prod.min.js:315 WMETB-JNF: Toolbox 0096 starting
WME_Toolbox.prod.min.js:316 WMETB-JNF: Checking API
WME_Toolbox.prod.min.js:4 [Violation] Handler took 1361ms of runtime (50ms allowed)
[Violation] Long running JavaScript task took 1362ms
VM206710:32 WMETB load app
VM206710:34 WMETB inject app
[Violation] Long running JavaScript task took 275ms
WME_Toolbox.prod.min.js:946 WMETB: all requires loaded
WME_Toolbox.prod.min.js:5 WMETB: FP loaded.
FancyPermalink.min.js:1 WMETB: running FP 2.4.2
FancyPermalink.min.js:10 WMETB-FP v2.4.2 - ready
FancyPermalink.min.js:10 WMETB-FP v2.4.2 - init done.
WME_Toolbox.prod.min.js:745 WMETB: creating overview map
livemap?lat=30.452517960867368&lon=-91.18721120874353&zoom=9:23 GET https://www.google-analytics.com/analytics.js net::ERR_NAME_NOT_RESOLVED
(anonymous) @ livemap?lat=30.452517960867368&lon=-91.18721120874353&zoom=9:23
(anonymous) @ livemap?lat=30.452517960867368&lon=-91.18721120874353&zoom=9:24
[Violation] Long running JavaScript task took 651ms
WME_Toolbox.prod.min.js:488 WMETB: Initializing layers
WME_Toolbox.prod.min.js:490 WMETB: Layers initialized
WME_Toolbox.prod.min.js:744 WMETB: Setting last forum check value to 1488292828313
WME_Toolbox.prod.min.js:930 WMETB: Enjoy!
WME_Toolbox.prod.min.js:246 WMETB-JNF: API check OK
WME_Toolbox.prod.min.js:307 WMETB-JNF: loading options
WME_Toolbox.prod.min.js:310 WMETB-JNF: Hook
vendor.legacy-c757b70….js:4 [Violation] Handler took 349ms of runtime (150ms allowed)
[Violation] Long running JavaScript task took 352ms
[Violation] Long running JavaScript task took 290ms
2WME_Toolbox.prod.min.js:535 WMETB: saving options
[Violation] Long running JavaScript task took 206ms
WME_Toolbox.prod.min.js:535 WMETB: saving options

[jm6087]

@jm6087

@BellHouse

@RussPA

Toolbox also does not seem to always remember the last 5 settings below the toolbar configuration settings, like the “Convert permalinks to production WME” setting (which always turns off when switching to beta).

I can duplicate setting “Convert permalinks to production WME” getting lost. Which other 4 are you referring to?

I have noticed the same issue. Additionally, the checkbox is lost on a hard refresh of WME Beta as well.

Just checking to see if you have been able to figure out why the “Convert permalinks to production” button isn’t staying checked?

[BellHouse]

@jm6087

Just checking to see if you have been able to figure out why the “Convert permalinks to production” button isn’t staying checked?

Yup, that’s fixed in our dev version, so in the next release this will be cured. The cause was rather trivial: I had accidentally erased one line too much from the Tb code for WME beta. :roll: