Dave2084 wrote:Also it seems to have broken the papyrus extended tools greasemonkey script (in firefox anyway)

A new version (1.3.0) was released this evening, and it is working for me on FF 9.0.1 on both Win7 and Linux (OpenSuse). If you are referencing it from the standard location (http://waze-papyrus-extended-tools.goog ... ze.user.js), it should start working again once you refresh your browser.

Starting some time this morning, the bug in which deleting a junction messes up the "Properties" display has returned. Upon deleting a junction, the "Properties" window only displays "ID: nnnnnnnn". When a segment is selected on the map, details of the road do not display, and turn arrows do not appear on the map. The road is highlighted, but the editor behaves as though the road is not actually selected.

slicer wrote:

wroadd wrote:Add-on creators!
The xxx.waze.com/cartouche is redirected to https://world.waze.com/map-editor/
please, check it out! This little change will "kill" the add-ons!

It's done for the Extended tools script, but must use the link for chrome (which is working with ff too )

Unless the link has changed (I am using http://waze-papyrus-extended-tools.goog ... ze.user.js), the script is still only set up to activate with /cartouche/, not /map-editor/.

harling wrote:Starting some time this morning, the bug in which deleting a junction messes up the "Properties" display has returned...

Also just noticed: if you hit "undo" after deleting the junction, the Properties window only displays the status of the junction that you deleted;e.g.:

All Connections enabled.
Disallow all connections
ID: nnnnnnnn

And that content, too, is "stuck" in the Properties window until the page is reloaded. Pending edits still seem to save correctly, but there's only so much you can do in this state.

slicer wrote:Try this : http://waze-papyrus-extended-tools.goog ... me.user.js

That works. Unfortunately, the "Open in" links still don't--at least not in FF. But I'll take activity on the project as a Good Sign™ (despite having built "chrome" into the script name).

When bridging two segments (e.g., an overpass erroneously junctioned to an underpass):

Click on the first overpass segment --> segment properties appear in the Properties window
Click on the second overpass segment --> properties of both segments (e.g,. segment IDs) appear in the Properties window
Click on the "bridge" icon --> segments are bridged, but both original IDs remain in the Properties window as though the bridged segments are still selected separately
Select a segment --> now all three segment IDs appear, and properties that are not in common with all three segments (level, name, city) are blanked out.

In fact there seems to be no way--again, short of reloading the browser--to clear this selection of the two original segments from the Properties window.

I will take this opportunity to mention again: the bug when deleting a junction, which was briefly fixed, is still there.

Under the circumstances, I don't look forward to "cartouche_old" going away. Especially if the new editor will have no capability to handle alternate names, which my area uses heavily for numbered "state routes" that are basically two-lane roads running through town after town after town under various street names.

AlanOfTheBerg wrote:

harling wrote:Click on the "bridge" icon --> segments are bridged, but both original IDs remain in the Properties window as though the bridged segments are still selected separately

Not for me. The properties toolbox goes blank and no segments are selected . Bridging works normally.

Is this another FF vs. Chrome difference? Does deleting junctions still work on Chrome? Both the released WME and the Beta editor have this problem for me on FF 9.0.1, on both Win7 and Linux.

BTW, I discovered that if you 'undo' the bridge, then select and deselect the original segments, they are cleared from the Properties winow and everything operates normally again.

I'm guessing the problem is something akin to assuming that the host browser will initialize certain local variables/arrays automatically, and one browser does and the other doesn't. Probably the same bug that causes the junction problem: when something that was selected is deleted, it remains "stuck" on selected, until you find a way to deselect it. I just confirmed that, after deleting a junction, if you undo the delete and then select and deselect the junction, the Properties window does clear and works normally again.

(FWIW, best coding practice is to explicitly initialize all variables, whether or not the runtime environment is "supposed to" do it for you.)

FWIW, FF10 on Win7 seems to have fixed the problem I reported earlier with the Properties display upon deleting a junction or bridging segments.

Spil wrote:BTW, if you click the junction but the trash-can icon stays grayed-out, that means that the junction can't be deleted at that time; that's when you'll need to check to see that the segments are: 1) in the same country, state (if applicable), and city; 2) the same name; 3) the same type; and 4) the same direction (and not "no entrance").

On point #4: there are many places in my area where it would be really helpful to be able to delete junctions between "no entrance" segments, without having to change their directionalities first. (Been saying this since Cartouche, but it could happen.)

koabal85 wrote:Before going Beta, I'd like to give a brief list of the things I'd like to see available from the old editor:

• "Split road into two one-way roads"
  ...

Respectfully, IMO this is one feature that we are better off without. Others' experiences may vary, but in my area, I have spent countless hours un-splitting roads that had been unnecessarily split; but never once needed to use this feature to split one. Having this feature only makes it more likely for an inexperienced editor to turn a simple map into a complicated one, for no good reason.