Honestly, I can't remember what the reason was - I'll look at the alternative method again when I prep the 0.9 release.

[edited to add] Already made this change in the current work in progress code

For all you userscripts.org afficionados, 0.9 has now been uploaded...

Changes relative to 0.8.7:

- Uses WME functions to determine current lat/lon and map viewport boundaries
- Allows bounding box to remain visible when panning/zooming

This latter change is the one most of you will notice straight away... Now, once you have a streetname radio button selected (other than the "Un-named segment" one), and at least one segment selected, the bounding box highlight will remain visible as you pan or zoom, which makes life easier if you're trying to name a particularly long road, or one where you need to zoom in and out to find all the tiny segments inbetween junctions. To clear the highlight, either select the "Un-named segment" radio button, or deselect all segments and then highlight one again.

Notes:
1. the bounding box will also remain visible if no segment is selected, provided you're then careful not to highlight any segments whilst panning/zooming - it's the act of forcing a new OS data search (by highlighting a segment when there are no segments already selected) that clears the current box.

2. when panning, the bounding box tracks in realtime if the aerial images layer is turned on, otherwise its position will only change once you stop panning and release the mouse button. I haven't deliberately made it work this way - the bounding box simply tracks the current lat/lon value presented by WME, and WME only updates this in realtime when the aerial layer is switched on...

Yeah, Tim's just PM'ed me with the good news... Unless he fancies rewriting it, we'll just have to wait for the beta version to be rolled-out to the great unwashed (i.e. those of us without access to the beta test) before I can fix it myself.

leocylau wrote:

Dave2084 wrote:This is broken in the current WME beta (it has broken all the scripts I use).

Not only WME beta I think. At least I can't use all the scripts on ff.

I can't get logged into WME right now, so maybe there are some changes afoot behind the scenes...

No changes yet to support the beta version of WME, but for those of us on the regular version, 0.9.3 brings a few minor bug fixes and tweaks:

* Removed the now redundant link to Cartouche
* Street names no longer feature trailing spaces (which, fortunately, WME seems to strip out itself anyway, but it's preferable not to feed it dodgy data in the first place...)
* Abbreviated forms of street names are no longer used in names such as "The Parkside" (which previously would have been abbreviated to "The Pkside" )
* UI now has three radio buttons so you can explicitly choose whether to use the existing city name, clear the existing name, or use the new name entered in the script UI
* A confirmation dialogue will appear if an attempt is made to copy the UI city name into the properties of a segment more than 1000m away from the point at which the city name was last changed or confirmed - this should (hopefully!) reduce the risk of forgetting to change the name as a renaming session proceeds across the map...

http://userscripts.org/scripts/show/137249

I changed the bounding box behaviour to prevent it disappearing when you drag or zoom the map. As a result, the current box persists until you either clear the existing highlight and then highlight a new segment, or select the "un-named segment" radio button.

Pleased to announce the latest, beta-friendly, version of this script

For beta users, you'll now notice a thin yellow bar underneath the tab area on the right of the screen. As you hover over a road segment, this bar will update to show the number of OS Locator matches at that location, along with a [show] link. Clicking this link expands the bar to full height, revealing the original script UI, which behaves just as in the non beta version of WME

For non-beta users, other than the addition of the matches total at the top of the UI, the only other change you might notice is that, the first time you try using a new city name, you don't need to click the Copy to Properties button twice for it to be copied into the segment properties field.

http://userscripts.org/scripts/show/137249

1.1 is now available... Only one change, the locator results box is now minimised by default in both the beta and non-beta versions of WME, and is now maximised on mouseover rather than via the show/hide links.

This change to the behaviour in non-beta WME prevents the locator results box from disappearing off the bottom of the screen if you're also using the latest version of the Colour Highlights script, as that now requires more space to show the turn and average speed data when you've highlighted a segment... It may also be of use to editors using screen resolutions lower than 1200 vertical, or if you happen to be editing in areas where the road layout is such that there are often more than 4-5 search results for each segment.

It also means that the code now behaves the same in both versions of WME, which might help ease the transition from one to the other once the beta version gets rolled out publically, and it makes code maintenance just that little bit easier, which is no bad thing from my perspective!


http://userscripts.org/scripts/show/137249

Sunday, a day of rest... unless you're a codeaholic

Having spent a few hours yesterday naming segments, I realised that more often than not I was selecting the street name from the top of the list and then having to move the mouse pointer all the way down the popup box to reach the Copy to Properties box which, given how tall the box now is with all the city name controls in place as well, didn't feel terribly ergonomic... So the first thing to change in v1.2 is the position of that button - it now lives at the top of the popup.


The second change will be noticeable only to AM and above level editors. dknight suggested it way back in the early days of the script, but at the time I didn't think it made sense to add it since the script didn't support city names. Superfraggle has recently suggested it again, and now that the script allows city name editing I couldn't think of a good reason to avoid implementing it any longer. So, AM+ level editors will now notice the Copy to Properties button has been renamed as the Apply to Properties button. A subtle change, but one which means that you no longer need to click the Apply button...

Been testing it here for about an hour, and although it takes a bit of getting used to (without the manual click on apply, you don't get the same visual and tactile feedback that the properties actually have changed) the result is a noticeably smoother/faster edit process.

http://userscripts.org/scripts/show/137249

I'd seen it do the open/close argument once in a blue moon during development so didn't think too much of it, but having now spent more time deliberately trying to provoke it I see how annoying it would be if it was being triggered more often... sorry about that.

1.2.1 now adopts a hybrid auto/manual scheme for controlling the popup behaviour - my goal was to eliminate the maximise-minimise-maximise-minimise-repeat ad nauseum issue whilst minimising any additional actions required by the user, and I think/hope I've achieved this by retaining the mouseover behaviour to maximise the popup, but requiring a mouse click to minimise it again. This click can be either on the