Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Re: [Script] WME Fix UI v2.54 -- 2021-02-25

Post by iainhouse
Version 2.54 has been published on GreasyFork. :mrgreen:

I reported the bug with the report panel at approximately 2am this morning. About 10 hours later, staff reported it was fixed in both Production and Beta - an impressive turnaround. :D

So this new release removes the fixes I introduced for the bug and also removes the highlighting of the panel-container div as a map blocker. Although it's still there, and big, it no longer responds to mouse events (only the actual report dialog does), so it no longer blocks the map behind it.

This change they've made also rescues the Draggable Panel function. Although the div gets left on the map after dragging & closing the report, it no longer blocks the map so it has no effect on anything. So this release re-enables Draggable Panel as well.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54 -- 2021-02-25

Post by iainhouse
Sebiseba wrote:Hi Iain,

Can you add an option to disable SV window size change ?
It's ID 'street-view-drag-handle'

Thanks !
Hi Seb. I suppose I could, but I don't think I will. :lol:

I guess you're referring to the invisible strip down the middle of the screen between the map & GSV windows? It's stupid; inconvenient. It's a very bad UI decision made by Waze and I wish more people had complained about it - they might have changed it.

I've already dealt with it in 2 ways. The first, is that I've classed it as a map-blocking bug. If you tick Show map-blocking WME bugs, it will be highlighted with a transparent red background, so you can see where it is.

The other way is the function Minimise GSV drag handle. That removes the invisible strip and replaces it with a clearly visible control that only covers a tiny portion of the map, is always visible, and (I think) fairly obviously shows what it does. You can also resize a changed width back to default by double-clicking the new control.
handle.png
(20.82 KiB) Downloaded 270 times
It doesn't "disable SV window size change" as you asked - instead I think it makes the ability to change the SV window size less of a problem and more of a useful feature. Also, don't forget that WME FixUI can change that default width of 50% (although that may cause problems with Firefox). :mrgreen:
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54 -- 2021-02-25

Post by iainhouse
dchary2418 wrote:There should be one option to move the Area Manager layer way to the back. Surprised nobody has thought of this
Can I ask why? I don't normally have it on but, as far as I can see, it's just a set of transparent shaded overlays.

It doesn't block anything, or interfere terribly with what else is visible. It's not like the GSV/Segment layer issue, where the GPS tracks can hide the segments.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54 -- 2021-02-25

Post by iainhouse
iainhouse wrote:
dchary2418 wrote:There should be one option to move the Area Manager layer way to the back. Surprised nobody has thought of this
Can I ask why? I don't normally have it on but, as far as I can see, it's just a set of transparent shaded overlays.

It doesn't block anything, or interfere terribly with what else is visible. It's not like the GSV/Segment layer issue, where the GPS tracks can hide the segments.
BTW, your signature link is broken - it points to waze.wiki.com, which is now gone. ;)
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54.1 -- 2021-02-28

Post by iainhouse
Version 2.54.1 is published on GreasyFork.

If you've read the last few posts, you'll remember I mentioned an "Easter Egg". This is an Enlarge Geo Handles feature I'm working on. I should have commented out the current code (only 2 lines!) before releasing 2.54, but I forgot. I'm a little saddened that the only comments are against it - but only a little. ;)

JustinS83 has a standalone script to enlarge segment geo handles. His WME PIE script has the same option for area places. But a couple of WME releases recently have broken this by changing the names of internal style rules that Justin is targeting.

This is my attempt to do the same thing - but in a different way, using CSS and targeting the named map layers that contains segments and places. I need to keep my code running through a few WME updates to make sure it continues to work reliably. Should the feature make it to release, it will (of course) be optional. It may well be configurable, might also cover the geo nodes themselves (as opposed to the handles between them), and might affect segment widths as well.

In case you're wondering why? I'm not as young as I used to be. Small laptop screens, tired eyes, late-night editing mean that enlarged geo features make WME much more pleasant to use.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54.1 -- 2021-02-28

Post by iainhouse
atrophicshiner wrote:I was reserving judgement on the geonode enlargement, I really liked that it was easy to spot the centre point of a segment, sometimes it took me a few tries just to locate them, the size is large but only by a fraction. How much work would it be to allow user preference on the size, 1x being original size, 1.5x, 2x, or such like.
The code to change the geonode size is literally one line of my script:

Code: Select all

addGlobalStyle('#' + W.map.getLayersByName('sketch')[0].id + '_vroot [id^="OpenLayers_Geometry_Point_"][fill-opacity="0.6"] { r: 8; }');
It's the code that has to go around the option that takes the effort: creating a new settings item that has to be loaded/saved/given a default value; presenting a new option in the script UI; creating events to handle changes; creating the function to make/clear the changes. That could well be an extra 50 lines or so.

If/when it does come, I might well provide value spinners for the various bits I'm changing. Or I might just make it an on-off option. I'll see how I feel about it. :P
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54.2 -- 2021-04-11

Post by iainhouse
Version 2.54.2 is published on GreasyFork.

This is a minor update to deal with my new script: WME Presets.

I've previously had to make adjustments to avoid interfering with other scripts. In this case, the opposite has happened. I designed a new script which assumed the interference from WME FixUI would be there - meaning it doesn't work well when for people not using FixUI. :oops:
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.54.2 -- 2021-04-11

Post by iainhouse
EloheiYishi wrote:The settings for the interface were reset. Maybe not a problem for those that have everything by default and changed, but not the general case. So I had to reset everything to fit my usage preferences. This shouldn't happen during updates. However, it may be coming from a previously disabled script.
In the entire history of this script, I only recall one single report of saved settings being lost before. Given the fact it works for 4000 installers over 5 years, I'm not going to worry unless it becomes a widespread issue. The saving method I use is the same as many other scripts.
EloheiYishi wrote:Also, the 1523-1524 rows overlay should be an option. I don't like it.
Not an issue, if you remove the buttons, which I would love to do, but I am used with the newer design and don't want to revert back. However, the UI changes need work to better fit in the design and the current placement and vision is not satisfactory for me, sorry.
I presume you are referring to Highlight Map Blocking bugs - which IS an optional feature! I don't know what you're talking about with the rest of that section.
EloheiYishi wrote:-> P.S. The .fa class has a "font-size: inherit;" option, which corrputs the display. I am not sure exactly why yet, but it leads to an increase in the div height from 56 to 64 thus gluing the Save button to the bottom. Turning this style option off fixes the problem and reduces the size of the additional buttons to the left of the search field. Having said that I recall you objected to moving things around and I generally agree, so I would prefer those button to be put elsewhere and keep the position of the search field. Also, those buttons are for editing preferences and their place doesn't seem to be there.
Again, no idea what you're talking about here. Where is the .fa option you're referring to. What div is increased in height? You mention multiple buttons but I've no idea what buttons you mean.
EloheiYishi wrote:It seems that the option "Hide Links panel" is outdated, am I right?
Probably.
EloheiYishi wrote:The Remove floating buttons has a bug in the display of the footer. It doesn't display properly and is moved when refreshed from the left to the right side of the other extension buttons.
I've no idea what you mean about moving. I place it on the RH side of the other extension buttons, so I don't see how it could be moving. But I agree there are some bugs with regard to the button shape/size/alignment under certain FixUI settings.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.55 -- 2021-05-09

Post by iainhouse
Version 2.55 is on GreasyFork.

YAY! Waze have made yet more apparently pointless changes to the WME Toolbar. Not important ones, like making sure it doesn't disappear to the right on small screens. Or improving contrast, or layout, or consistency. No - they've just made the document structure more complex and, in the process, affected any script that adds buttons there.

The disappearing Refresh button is because the re-arrangement caused the Remove floating buttons from map area function to move the refresh and layers button inside the divs for other buttons! I'm not sure what was then killing the Refresh button - most likely something pointless like WME deleting & recreating a toolbar button for no apparent reason. Anyway, I've fixed the Unfloat function so the buttons once again get moved to the Toolbar as separate buttons - not inside others.

The extra padding on the right of the buttons is also my fault. Actually, no it isn't my fault at all - it's yet more stupid design from the geniuses in the UX/UI department at HQ. If you're using a small screen, the edit buttons don't fit and disappear off the right of the window. I was fixing that with a min-width:430px style on the edit buttons. I guess they've changed something so that the contents of the edit-button div now left-justify. I've updated the min-width to be a variable size, based on the number of buttons present; whether or not I've added to them by unfloating Layers & Refresh; whether or not I've compressed them. This has eliminated the unexpected right padding and should still help on smaller screens. However, it doesn't account for any other scripts which might add edit buttons (like Bookmarks and WECM). There's only so much I can do to compensate for someone at HQ who didn't do their job right in the first place.

One of the UK Champs asked last week "What is this Headlight Required box in segment properties?". Yes, for those of you who have also forgotten, Waze introduced a new feature used only in a few countries and dumped yet another UI element into WME that was useless to most of us. At the time, I added the function to Compress/enhance side panel contents to hide it based on the country settings. That feature broke recently. Plainly it's been working so long, some people have forgotten that useless checkbox ever existed. :lol: Well it seems that the relevant part of the W model is now loading so slowly that the country setting I check doesn't exist when I come to check it. I've therefore added a second check with a 5-second delay. If the checkbox doesn't disappear immediately in a non-headlight-checking company, it will do so a few seconds later.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Re: [Script] WME Fix UI v2.55 -- 2021-05-09

Post by iainhouse
linguasaltitante wrote:Probably this is to be fixed on WME side, but: is possible to resize the sub-menu window of road shields in order to accommodate the full length of instruction text that we see on top?
I haven't even looked at the new dialogues for road-shields; or lane guidance for that matter. Road shields are only just currently rolling out in production and, as you say, they should really be fixing the problem themselves. I hope you've submitted a bug report! ;)

In the fullness of time, I'm sure I will be smacking the new dialogues with the FixUI stick. :lol:
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
Locked