Just confirming: this issue still occurs on the latest v1.4-206.sketch wrote:Mostly just formatting stuff. The segment list and highlights button formatting have gone all wonky. The functionality otherwise seems to be unaffected.svx-biker wrote:Toolbox doesn't seem to work correctly with latest Beta 1.4.196
Segment list:
Actual size:
https://www.waze.com/wiki/images/6/6b/W ... _0M_6c.png
CM: Indonesia, Timor-Leste / Global Champ
iPhone 6s Plus | Waze Indonesia Wiki https://wazeopedia.waze.com/wiki/Indonesia
CM: Indonesia, Timor-Leste / Global Champ
iPhone 6s Plus | Waze Indonesia Wiki https://wazeopedia.waze.com/wiki/Indonesia
Beta URL has changed, please update to compensate the change. Great tool, thanks
https://www.waze.com/wiki/images/7/76/W ... 00k_4c.png
Area manager: Some cities
Country manager: Finland
Suomenkielinen Wiki | Asemien tarkistus | Editointiohje
i9300 | Resurrection Remix | Waze 3.9
Area manager: Some cities
Country manager: Finland
Suomenkielinen Wiki | Asemien tarkistus | Editointiohje
i9300 | Resurrection Remix | Waze 3.9
Hello,
Toolbox crashes on Chrome all the time.
I tried to uninstalled everything, deleted all usere data, ... but no improvement.
Any other tricks to suggest ?
Thanks.
Toolbox crashes on Chrome all the time.
I tried to uninstalled everything, deleted all usere data, ... but no improvement.
Any other tricks to suggest ?
Thanks.
- When using the script, moving on the map becomes relatively slow when there are many segments like in a city. If I don't stop, it crashes chrome or the computer (bluescreen)OyyoDams wrote:What do you mean ?Laurentwb wrote:Toolbox crashes on Chrome all the time.
- The problem disappears if I uncheck the options (like u-tuns, ...)
- I tried to remove the script and reinstall. No change
- I tried to remove chrome completely and reinstall. No change
- I tried to remove chrome and the script together and reinstall. No change
- (I'm not sure I found a way to remove 100% of the script. It seems that something always remains in memory, although I removed data manually from the appdata folder)
- I never had that in Firefox. I recently moved to Chrome because of issues with support to userscript.org
- I'm on version 1.4.1.5
The last thing I can report is that I use Validator and color highlight in the same time. This has never been a problem in Firefox but who knows ...
Best regards.
Should I then just uninstall and re-install the graphic drivers ?top_gun_de wrote:No web application should be able to crash your computer with a bluescreen, as the kernel and the drivers are isolated processes. Since Chrome uses graphics acceleration, it is probable that your graphics driver is faulty.
Regards,
Detlev
Thanks for a great script. I have problem that if I reduce the size of a MP or UR report by clicking on the Less button, I'm then unable to open it again by pressing the More button, or close the report, as the auto-hide button click detection area (the technical term escapes me ) is twice the size of the button and covers the two underlying buttons.OyyoDams wrote:Version 1.1.1.0 released!
Changes:
- Button at the top of the editor to toggle side bar auto-hide
Firefox 20.0 on Ubuntu 11.10.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Much better. Many thanks.OyyoDams wrote:Thanks. The bug occured when WME addons wasn't installed. Now fixed.LeighGr wrote:I have problem that if I reduce the size of a MP or UR report by clicking on the Less button, I'm then unable to open it again by pressing the More button, or close the report, as the auto-hide button click detection area (the technical term escapes me ) is twice the size of the button and covers the two underlying buttons.
Leigh.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Hi Oyyodams,
Finally, WME toolbox loads in Firefox without errors. Many thanks.
Though in the process I've discovered the floating toolbar is still there in Firefox. I'd been under the impression that Google had banned all of these tools, as it disappeared when I switched to Chrome, at the same time the new editor was released.
So, should I be seeing the floating toolbar in Chrome, or not seeing it in Firefox, or..?
Finally, WME toolbox loads in Firefox without errors. Many thanks.
Though in the process I've discovered the floating toolbar is still there in Firefox. I'd been under the impression that Google had banned all of these tools, as it disappeared when I switched to Chrome, at the same time the new editor was released.
So, should I be seeing the floating toolbar in Chrome, or not seeing it in Firefox, or..?
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Hi OyyoDamsOyyoDams wrote:It's tested and currently works in both Chrome and Firefox.LeighGr wrote:So, should I be seeing the floating toolbar in Chrome, or not seeing it in Firefox, or..?
Many thanks. That's good news. I'd seen references to other tools that offered permalinks to other external sources being withdrawn, and make the assumptions that your toolbar had been withdrawn in the same fashion. Pity, as it's an extremely useful set of tools.
Let me work out why it's not loading in Chrome.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Hi OyyoDamsOyyoDams wrote:It's tested and currently works in both Chrome and Firefox.LeighGr wrote:So, should I be seeing the floating toolbar in Chrome, or not seeing it in Firefox, or..?
Found the Toolbox toolbar in Chrome It had got itself pinned to the bottom of the frame, off the visible screen area . Fiddling with the visibility and position attributes of the WMETB_PopupDiv element made it pop back into the visible screen area, and it has now taken it's place at the top of the screen, where hopefully I won't loose it again.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
Re: [script] WME Toolbox