ojlaw wrote:hey there,
thanks for all the hard work on this script! i'm probably alone in wishing this but just thought i would ask. it seems the map blocking usually starts in the upper left corner of WME just under the zoom bar if "Move and restore zoom bar" is checked. i'm wondering if it would be possible to adjust the position of the zoom bar down so that it would be functional when the map blocking is there without first having to pan the map. thanks for your consideration.

It would - except it will clash with several other things which will all need moving as well!
Directly below Zoom, GSV and Location buttons, I have WME Map Tiles Updates; below that is WME BeenHere; below that I have my Toolbox arrow status panel.

At the end of the day, this is a serious and stupid WME error that they should have fixed by now. It is also affecting every user of WME everywhere - not just the 500 or so people who use my script regularly.

What I would really like is for as many people as possible to go here (warning: Beta WME users only) and ask why it hasn't been fixed yet. I'm getting tired of asking.

Teasers!

I've just spent a difficult 3 hours hacking away at the WME interface. Having succeeded I feel in a good mood, so here are some upcoming teasers for what's coming - once I've built all the infrastructure to make them controllable options.

GeekDriverPeaceful wrote:Can you also shrink the blocks in Alternative Names?

Sure. I think I forgot about that with the previous WME interface until someone reminded me.

Version 2.14 is published on GreasyFork.

This version brings 3 new features plus some more work on compression.

Bridge Button. This button joins 2 selected segments into one and raises the elevation of the new segment. This button presents two problems. First is that this functionality is rarely needed, but the button appears every time you select 2 connected segments. Second is that the button partially overlays the junction node, making it easy to press it accidentally. Fixing the button moves it up off the junction node. Disabling it is obvious. Since it is rarely useful, I have chosen the default options to be to move it AND disable it. Obviously, you can turn it back on if you want.

Start calendars on Monday. Both the closures and restrictions dialogues include calendar date pickers. These have not been localised (a reported WME bug), so they always have Sunday as the first day of the week. If you prefer Monday as the first day, now you can have it.

ISO dates in Restrictions dialogue. The dates in the restrictions dialogue are all in American MM/DD/YYYY format. Fine if you're used to it, confusing if (like a lot of the world) you're not. Again, this should be localised and isn't. There was some discussion among the UK champs as to what to change it to: DD/MM/YY, DD/MM/YYYY or even DD/MMM/YYYY (with an alpha month name like Apr). In the end, I decided the best compromise was to use ISO date format: YYYY-MM-DD. Whilst not quite as "natural" for many people, it's easily recognisable and understandable. It also matches the format already used for dates in the closures dialogue. This option defaults to on.

Lastly, as per request, I have done some compression work on alt names for segments. It's not a part of WME that gets greatly used, but one that badly needed it!

Twister-UK wrote:Sorry to be the bearer of bad news, but the date fixes you've just added seem to be breaking the TBR UI for me in both Firefox and Chrome and in both Prod and Beta WMEs, with no other scripts enabled...

You're absolutely right - and I should have spotted it.

I've been been doing all my testing picking random segments and adding new restrictions, so it wasn't obvious that this is happening with existing restrictions. But I was having trouble looking at the Richmond Park restrictions a few days ago - I should have guessed it was my fault WME was acting screwy.

I knew something was odd about the datepicker in the restrictions dialogue. If you look at the mutation observers in the code, you'll see where I change the format the "proper" way for closures but had to do it differently for restrictions - obviously that method is having unintended side effects.

So I guess those options will need some more work. I just hope I can find time before next week.

bz2012 wrote:Problem: if I 'compress/enhance bars above map' then I can not click on "enter snapshot mode', nor can I leave it via that button if I compress after entering.

I don't know what's causing that. It's probably not simply WME FixUI, but an interaction with one of the many other scripts you have running.

Two things you can try. The first is to right-click on the inactivated link and select "inspect". That will open the developer console with that element highlighted in the page source. The element that should be highlighted is <a class="toggler">Enter Snapshot mode</a>. If that isn't what's highlighted, post a screenshot of what is.

The other thing you can try - and I know it's a pain - is disable scripts one-by-one until the problem goes away. Or turn them all off (except WMEFU) and then turn them on one-by-one until the problem occurs.

If it's due to interaction with another script, I might be able to produce a workaround.

Version 2.15 is up on GreasyFork.

This is a fix for the problems mentioned above with the dates in the Restrictions dialogue: dates for existing closures are no longer wiped from the date picker.

There's an added side-effect now, which I am choosing to describe as a bonus improvement to the UI. If you go to create a new restriction, the date range button will now show "undefined - undefinded" instead of the default "today - today+1 month". The defaults are still there if you open the calendars but technically (according to me) the dates aren't defined until you've set something.

CitizenTraffic wrote:Just updated to v2.15. When I did, I noticed the Chat button is now covered by a red box. Added screen shot.

This is a new feature introduced in 2.13 on 9th March.

iainhouse wrote:First is a new function: Highlight Invisible Mode. When you're invisible, the Wazer on the Chat icon changes from light blue to grey. A typical example of inadequate contrast provided by Waze. I got caught out myself by this the other night, not realising I was invisible. And the next day, MagnoBe contacted me to say he'd developed a script to force visibility to stay on - would I like to incorporate it into WME FixUI?

I thought about it quite a bit, but it doesn't really fit. I prefer to try & stick to changing the UI, rather than adding editor functions. Plus it's not the sort of thing I would personally use. But if you want this function, please have a look at WME Status always visible - and don't forget to hit the thanks button.

In the meantime, what I have added to WME FixUI is a change to the highlight. Now, when you're invisible, the chat button will turn a slightly-translucent red. Much more noticeable, I think, without being too garish.

bz2012 wrote:A modified 'binary search' fingers "WME Maximized (Basic rickzabel edits) 0.6.6(Beta)" as a co-factor in the problem.

I was under the impression that script was long-since-abandoned; well before the new version of WME even arrived! In fact, it was partly the inspiration for me starting WME FixUI - I wanted some of the functionality of that script but not all of it - and it was an all-or-nothing script. That's why all of my changes are split into selectable options. If WME FixUI and WME Maximized can co-exist properly, I would be amazed.

bz2012 wrote:a 'binary search' is almost always faster than 'one at a time'.

You're absolutely right. but I'm not going to suggest that to someone who might not know how to do it. It's bad enough trying to diagnose the initial problem = never mind then trying to diagnose a problem with the way someone has implemented binary search.

CitizenTraffic wrote:Well, I like the feature of letting me know when I'm in Invisible Mode. However, I generally do not use this mode, so for it to turn on without my help is a problem.

Just to be 100% clear, WME FixUI did not turn on invisible mode. You did that. WME FixUI just made the fact you were invisible more obvious to you. It seems that, had the script not done so, you wouldn't have realised you were invisible. That is exactly the reason for adding this function.

Generally speaking, the options I add to the script are there to improve WME. Some of the features will be turned on automatically the first time they appear on your PC (when you install for the first time or update to a version with a new feature). After that first time, you can change the option and I will never change it again.

It is a matter of my personal opinion as to which features do this. If I think the feature is beneficial and does no harm, or corrects a genuine bug in WME, I may choose to turn it on first time. For example Highlight Invisible, Hide User Info, relocating the Zoom bar & Chat icon. If you don't like my choice you can easily change the setting and you only have to do so once. If you really don't like my opinion, then maybe my script isn't for you.