[Script] WME Toolbox (until 1.5.9, now archived)

doctorkb · October 16, 2014, 11:58am

Yes you get the list, but have you tried adjusting anything? It’s been broken for me since the latest big WME release.
Probably. will add to list of requests

Arnoniem · October 16, 2014, 3:27pm

hmm. ok so that’s the issue. Thought i did that at home, but here at work it doesnt work

ottonomy · October 17, 2014, 6:07am

Maybe I’ve forgotten how to search, but I can’t find any discussion about the status of Toolbox’s Snap Distance setting since WME broke it. Is that amongst the things for which fixes are actively being pursued?

BellHouse · October 17, 2014, 8:40am

Yes, we have fixed that, it will be included in the next release (which is expected for end of this or beginning of next week).

davielde · October 17, 2014, 11:06am

We’ve also set a max value of 30 pixels whereas there was no previous maximum. If anyone feels that they would need a higher snap value, please state your case. The min shifted from 0 to 5 as well because at 0, nothing snaps.

doctorkb · October 17, 2014, 1:22pm

The min needs to be 0 – meant to comment in the Hangout, but didn’t in time.

There’s a good case for turning off snapping in some cases when you’re working on some fine adjustments. Though perhaps a “0” setting really means “1” – so you can still connect nodes, etc.

davielde · October 17, 2014, 1:44pm

Changed, tested, and pushed. The code now checks for a tolerance of 0 pixels and assigns it 1 pixel. After about a dozen attempts, I could snap at 1, so it still functionally acts as 0 unless you are really determined.

ottonomy · October 17, 2014, 4:15pm

THANK YOU! (sorry for shouting… this is huge for me)

Indeed. I typically leave snap set to 5, but often toggle it to zero for precision adjustments.

That sounds good. Thank you, all of you, who are working so hard to maintain and improve Toolbox!

crazycaveman · October 17, 2014, 6:11pm

Can I ask what is meant by snapping? Is this for snapping a node or geometry point to another road? I’ve seen this in the settings but was unsure what it did

davielde · October 17, 2014, 6:21pm

Yes, it’s the distance in pixels at which whatever you are dragging will “snap” automatically to another object like a node or segment.

I feel like such a pro answering that, but I had a similar question myself a few days ago . It was a setting in the Config Panel that I had never touched.

For anyone interested in more technical detail: Snapping

KB_Steveo · October 18, 2014, 12:34am

I’m having problems with “Redo Roundabout”. All it does is delete the roundabout that is there (Chrome & Toolbox 1.4.7.0)

kodi75 · October 18, 2014, 1:12am

So not everyone here is an AutoCAD / Microstation hack!

doctorkb · October 18, 2014, 2:44am

Do you have JNF installed separately?

This has been addressed several times should be completely fixed in the next release (within the next 72 hours or so)

Olestas · October 18, 2014, 5:34pm

I see this text sometimes:

[JNF Toolbox 0093]JNF script not active. Upgrade!
For a full explanation, see this page.

But Toolbox as JNF inside, why would it recommend to install it?

doctorkb · October 18, 2014, 7:10pm

That doesn’t look like a TB message. Is there another script installed, perhaps called JNF Toolbox?

BellHouse · October 18, 2014, 7:58pm

Where do you see this text?

Olestas · October 18, 2014, 7:58pm

After disabling scripts one by one I found it to be WMECH. Will write there.

rulikoto · October 18, 2014, 9:13pm

Can’t wait any longer [emoji3]

Sent from my Nexus 5 using Tapatalk

PesachZ · October 19, 2014, 5:29am

ottonomy:

BellHouse:

Yes, we have fixed that, it will be included in the next release (which is expected for end of this or beginning of next week).

THANK YOU! (sorry for shouting… this is huge for me)

doctorkb:

The min needs to be 0 … There’s a good case for turning off snapping in some cases when you’re working on some fine adjustments…

Indeed. I typically leave snap set to 5, but often toggle it to zero for precision adjustments.

davielde:

Changed, tested, and pushed. The code now checks for a tolerance of 0 pixels and assigns it 1 pixel. After about a dozen attempts, I could snap at 1, so it still functionally acts as 0 unless you are really determined.

That sounds good. Thank you, all of you, who are working so hard to maintain and improve Toolbox!

Thanks a lot. Like ottonomy my snap level never goes above 5 either, though I do occasionally bring it lower (or zoom in more).

Sent using Tapatalk for Android 4.4.2

doctorkb · October 20, 2014, 2:18am

New version (1.5.0) published for FF. Chrome to follow in morning.

CHANGELOG:

1.5.0 (20141019)
New: Places list (#20)
New: "Zoom to" functionality in segment and places list (#21)
New: Message reports unread PMs in forum after WME start-up and in regular intervals (#45)
New: SegmentID as new column choice in properties editor (#101)
Fix: Toolbox now works again in beta WME
Fix: Properties editor (#73)
Fix: Snapping distance control (#71)
Fix: Copy segment attributes
Fix: Incompatibility with external JNF script (#88)
Fix: Add roundabout place (#80)
Fix: Count and logic of magic fix u-turns and revcons (#100, #102)
Fix: Missing road types in segment list (#93)
Fix: Allow all connections on screen (GC only) (#95)
Fix: Allow all connections in area place (GC only) (#96)
Fix: Some functions affected segments not on screen (but shouldn't have) (#52, #63)
Fix: AM list wasn't complete (#56)
Update: added some higher quality FancyPermalink (FP) icons
Update: FP link updates for Greece, Israel, Italy and Argentina
Update: FP unlock links to Google forms for several countries (#92)
Update: Improved column sorting in segment list (#85)
Update: Highlight of unconfirmed turns now available only to CM/L5+ (#94)