sketch wrote:In playing with settings and the bridge button... I thought I might make a suggestion as to what you decide should be a default.

It may be a better strategy, simply to prevent wasting everyone's time, to make any feature that may be interpreted as a bug in WME default to "OFF" on first run. That way, we don't have dozens of posts both here and in the WME feedback threads saying "Y U PUT RED BOX???" or "I CANT BRIDGE NO MORE!!!!!!!!" because anyone who comes across this will know about it because they personally had to turn the feature on.

It's a fair point, but it also highlights a couple of problems that really aren't my fault.

The red box highlighting the GSV element that blocks access to the map: that is a genuine and stupid bug in WME. Yes, I've kind of taken the flak for highlighting it - but it's a bug that affects every user of WME across the world, most of whom can't work out why they sometimes can't select anything but haven't reported it because they can't reproduce it. Waze HQ have acknowledged it - in a Beta bug post not accessible to the vast majority of WME users and they still haven't fixed it, despite a fix being trivial. Massively more trivial than, for example, and Expert Mode April Fools joke that is still around a week later.

I made a deliberate decision to highlight rather than fix the bug. That way, users of my script are able to dispense with the confusion as to what's happening. The discussion also serves to highlight to everyone that the bug exists - and that there is a script that can do something about it, quicker than Waze HQ.

Having said all that, the map-blocking bug is a special case. I think I will continue to be guided by my own opinion as to whether or not to turn on new options. But my opinion has definitely been wrong a couple of times before, so I also carefully consider where I got it wrong in the past when I turn on a new option.

The other problem is much simpler. People aren't reading the "Updated" pop-up or the release notes for new versions. The pop up lists every new feature, including major ones from past releases. The release post gives details of all features and changes, including whether a new feature is going to be on by default. I can't really force people to read them and I don't want to put things in the way of someone who just wants to get something edited and doesn't want to read a release note now. But I am considering a couple of possible extra notification options:

• An additional modal dialogue (one you have to click on before you can proceed) to warn of a new feature being disabled. Either one dialogue per new feature or one for all new features
• A delayed pop up that will show up a little while after WME has loaded - it won't stop you doing anything but will need to be manually dismissed
• A non-modal dialogue that links to the release notes on the forum topic. It would re-appear once per session until you've actually visited the forum page

I don't know. These are just ideas, one of which only occurred to me whilst writing this post. They'd all need me to learn/find some additional dialogue code. I might just leave it as is and let the discussions continue. After all, if I didn't have Waze users to talk to, I wouldn't have anyone to talk to.

Version 2.16 is live on GreasyFork!

This brings a far less controversial new feature - one that can only be enabled temporarily and will disable itself again on the slightest excuse.

A couple of nights ago, when answering a request from a level 3 editor, he pointed out a point Map Comment that had been dropped immediately on top of a junction node. Because the junction node takes priority on mouse clicks, he couldn't select the map comment to move/open it. Segments attached to that node were locked to auto(4), so he couldn't move the junction node. So he knew the comment was there but couldn't access it. He's also had similar problems with point places - and I've encountered both problems myself.

Even for a L6 global champ the options aren't great. I could move the junction, unnecessarily editing segments (lazy lack of workaround used by iainhouse). I could move the junction, select the comment, create a permalink, undo, then use the permalink (workaround by Vince1612). I could move the junction, select the MC, hit Undo and still have the MC selected (workaround by SpeedDzel). PITA, whichever way you look at it.

So my new feature is quite simple. A button on the FU tab that disables the junction nodes layer. It's purely temporary - you'd only need to do it whilst you moved the problem MC/Place out from under the junction. When you click the button it clearly highlights that you've hidden the junction nodes. As soon as you pan/zoom the map or refresh or save, junction nodes reappear automatically - all I have to do is reset my button.

Hopefully this will save you all from an occasional but annoying feature of WME.

I might be confused here, but can't you just turn off the places layer? There's even a keyboard shortcut - SHIFT-L - to do it instantly.

I do have enormous sympathy for editors who are unable to see vital information just because they are unable to edit it. I've lobbied strongly for this not to happen.

Having said that, Waze have always been responsive to our complaints about this. It seems to be a sort of development blind spot, rather than an intention to hide information. Indeed, HQ have identified it as a general problem and asked us to make it a "master" bug with "child" bugs for the individual problems of data hiding. That means the individual bugs can be squashed without allowing the main problem to be considered resolved until all the children are sorted.

That's not to say that I won't sometimes add something to WMEFU to deal with a bug of this type. If the information is literally hidden but present in the page, I can deal with it quite easily. But if the information isn't there to start off with, finding it & inserting it into the page is far more difficult.

The current Beta WME includes fixes for several incorrect-information-hiding bugs, so it's not an area worth my looking at until that version hits production.

Version 2.17 is published on GreasyFork!

This version is mainly to deal with some changes to WME that are currently in Beta and will be coming to productions. These are to do with the way the WME internals work and HQ are being extremely helpful about warning us of these upcoming changes in time to cope with them. None of that should affect production WME for now, so I'll post more details in the Beta topic for this script.

I have also finally confirmed something I'd suspected for quite a while. Average Speed Camera controls do not appear in WME unless ASCs are enabled for your country. That makes providing an option to hide them pretty useless, so I've removed it - although not without a pang of sadness at removing code I worked hard on.

jm6087 wrote:Is it something I am doing? My zoom bar won't move back to the top left side of my WME screen now.

That's in Beta, isn't it?

Sorry - I was a bit late posting the update details on the Beta topic for the script.

Oh dear. You'd have to go a long way back in this topic to find the people who complained about that after not reading the release notes.

You've got the Comments layer turned off. Editing anything is unwise if you can't see that someone has done something unusual and left a comment to explain it. And whilst it's often convenient to turn off the comment layer whilst you're working inside an area comment, it's also easy to forget you turned it off.

I consider having the Comments layer on is important enough that this option is turned on by default at first install of WME FixUI. Although you can, as with all the other options, turn it off and it won't re-enable itself.

G_W1Z wrote:I did try searching for the term yellow in this thread but didn't come up with any results

You wouldn't have found it - even if forum search worked properly, I describe that colour as orange!

The feature was introduced all the way back at the end of 2016, in version 1.6. I also note with some embarrassment that the feature isn't listed in the first post. I supposed I'd better make sure that's updated.

Even more embarrassment for me!

This feature was missed from the first post because, when I recently re-organised the first post, I must have accidentally removed the entry. The reason - it's not an optional function, so I didn't see it in the list of script options and forgot about it. So that also invalidates what I said above about being able to turn it off.

I didn't make it optional because I felt it was pretty important that editors kept the Comments layer on; and it's only a colour change in one part of the UI so it doesn't do any harm.

I've added it to the list of functions in the first post now. I've also described it as "orange/yellow" - who am I to say I'm a better judge of colour than you?

By default, no, but it is possible to assign a keystroke to toggle the comments layer. Press ? and the dialogue for checking/changing keyboard shortcuts will open. "Toggle map comments" is about half way down.

There are some other scripts that play with layer visibility - mainly to stop permalinks changing your layers. And the flipside of that is that you can open a permalink with a layers setting and that will change your layer visibility.