Fantastic work - as usual.

• "Bouncing Map Syndrome" is cured.
• "Permalink" is moved.
• Locality showing up beautifully. Even better: without a segment actually selected, you can now move across the map watching the box to quickly find the boundaries.

First off, not having to de-select before selecting another segment is great - now all I have to do is train my muscles to stop doing it anyway!

I would also like to second David's request to dock/hide it: maybe a checkbox to return it to the old behaviour?

I'm afraid to report that I am having a problem with the update. If I have the OSMC window enabled with auto-tracking, then focus keeps jumping to that window when I pan the map. I did quite a bit of experimenting last night: I can't pin down the reason 100% but, with about 90% consistency, it seems to be down to the speed I pan the map. Unless I pan the map very slowly, Chrome will switch windows to the OSMC.

It doesn't seem to be affected by how far I pan the map. I can also start slowly, "do a quick bit in the middle", then end slowly without a problem. It's so bad I might have to go back to the previous version for a bit.

Note that I am not using the beta editor (if there is one at the moment).

leocylau wrote:Normally I click the street name and a yellow rectangle box will be displayed on the map. It's gone now

I'm not seeing this problem - I can still see the bounding box(es).

The problem with jumping to the OSMC tab is fixed - many thanks.

Now I'm going to be really picky! If the floaty window is minimised near the bottom of the screen - such that it would go off the bottom when expanded, is it possible for it to expand upwards?

Twister_UK wrote:*bonnnnnggg* For iainhouse, the window is now shifted up if maximised at the bottom of the screen

Excellent!

Every time I think you couldn't make this script any better - you confound my expectations! Thank you, yet again. And I can entirely sympathise with the "working whilst a kid sits on you" problem.

The pre-select for last street name edited is working fine, as is the drop-down of cities.

I've been having a minor issue with the editor, that I've just pinned down to an interaction between this script and TimBones' Color Highlighting script.

I've just posted details here in his script's topic, so I won't repeat it all here, but I'm basically seeing the road & aerial images layers offset to the left immediately after permalinking or refreshing, cured by panning the screen.

Other than that, the new functionality looks good. I'm off to test it now!

As posted in the WMECH thread, it was the scrollbar, and v1.15.1 has fixed the problem.

I am getting that, but I hadn't noticed. I also hadn't noticed that I have somehow missed 2 updates , so I'm getting it with version 1.15.1.

However, I made the problem go away. What I actually did, was hit the link to userscripts & saw I was out of date, so I downloaded the new version. I then checked on the current version and saw the problem. Then I noticed something:

First, it's not a fixed amount of blank screen at the bottom. If you pan down gradually, the rendered map will almost reach the bottom, then suddenly the bottom will blank out up to about a quarter of the way up the screen. If I had to guess, I would say that the OS map is being rendered in tiles and was insisting on only showing complete tiles at the bottom margin.

Then, I noticed Chrome still had the Downloads bar taking up a bit of real estate at the bottom of the window. As soon as I closed the downloads bar, the problem went away. Finally I installed v1.17 and found exactly the same behaviour. When the downloads bar is visible, a variable amount of the bottom of the image is blank.

So I would say it's nothing to do with WMEOpenData at all. I think it is a very minor bug in the "OS OpenData Full Height" script that is having problems when Chrome is showing the downloads bar.

Maddeningly inconsistent!

I've now been trying for well over an hour to replicate this problem consistently - without success. I have managed to identify a completely different but with the script but I can't do it with the original problem.

First off, here is some output from my console on one occasion when I did manage to have the problem. This isn't the console on the OpenData tab - there's nothing in it. I'm also getting nothing appearing in the console when I actually click the link. However this is what I saw in the original WME console (after stripping out the irrelevant dross): I don't think there's anything helpful there. Now for the other bug.

If I open WME and do not mouseover any segment before clicking on the "OS OpenData" link, then I get a duplicate of my WME tab instead of an OpenData tab. It looks like the value for this link does not get initialised until the mouse passes over a segment - at which point the WMEOpenData box shows the "loading OS data" before showing a list of possible street names. After that, the link opens OpenData as expected.

As for my Chrome version - well it looks like there have been at least 2 updates today. Each time the version changes, ZoneAlarm will ask me if I want to allow the exe to access the internet - and that's happened twice today. Current version is "25.0.1364.152 m", running on XP SP3 with all updates.

Just had another idea for testing - I'll post again if anything comes of it.

I'm having a problem with the bounding boxes. I'm currently editing up in Dingwall in Scotland and I've been noticing that the bounding boxes are shifting from left to right as I pan the map.

In Dingwall it's been particularly noticeable. I just checked in Blackpool, where the effect is less pronounced, then down in Cornwall where it was even smaller. I'm guessing that it's connected to how far North I am - could it be some sort of coordinate conversion problem?

I also do not remember seeing this happen before the latest editor release, so maybe they've done something to alter the horizontal scaling factor for editor elements and it no longer matches what the script is doing.

Fraser Road is one example I've picked out. Interestingly, the ability of the script to choose the road in the list is unaffected: Fraser Road will always be top of the list when I mouse-over the same point in the segment - whether or not the bounding box is covering that point at the time.