LOL. 1.4.3.0 seems to have an issue forcing Chrome to install the new version from the Chrome store, but when it goes to the Chrome store it does not download it. I am stuck at 1.4.3.0.
New to Chrome, so not sure this is not somehow a problem on my side.
Ah. My error. Misunderstood your page. When it takes me to your page, it shows:
The reinstallation I took to mean “update” like I always did for Firefox.
I now see the link below that saying to go to the Update Extensions link. Maybe in the box above for Installation you can add:
“For Updates, use the Update Extensions button shown below.”
Also, on your page you have
“Declined” is not likely the word you want there. Maybe you are saying it is “built for 2 versions:”
I believe what is meant here " WME Toolbox has been split into two versions: one for the beats editor, and another for the production editor. "
In older versions versions it was one version that worked on both the beta and production editor. It was recently split into two.
the word split can be replaced with any of these:
forked
separated
branched
Chrome updates extensions in the background on its own, I believe also every time you restart chrome. Of you want to force an update (for a new version just released) you can try to restart chrome, or go to settings>tools>extensions> check the developer box on the top > click update extensions.
You will then have reload (PL) WME to use the new version.
Maybe this is a well known limitation, but I’m looking for solution in easy fixing soft turns on segments 1km+. Toolbox now perfectly identifies and fixes shorter segments with soft turns (Q+W). But as WME Validator identifies (example) also larger segments with soft turns, it would be nice for the same solution in this case. Thanks!
Why don’t you just click on the turn arrows when the purple ? icon shows? We’ve always been able to fix soft turns manually in WME, no need for a script.
I can´t update to 1.4.3.0 I’m at 1.4.2.9.
by the way, could you please add this map tool http://gaia.inegi.org.mx/mdm6/ , it is the National Institute of Statistics and Geography´s official map from Mexico, thanks
Of course - I can zoom in for every road segment and click on the arrows. But in WME arrows shows only at the first zoom levels. Junction node fixer and now WME Toolbox allows to fix them at higher zoom levels and save time.
It’s not the length that’s limiting, it’s just that the entire segment should be on your screen. So if you select one of the nodes, and then zoom out a bit, you can use the good old Q.
OyyoDams, could you make the segment list and properties editor so they can pop-out into floating windows, so I can keep them on another screen? I have two monitors but both are low-res, so they tend to get in the way.
could it be a popup window in another tab in the browser, like when you click “find member” near the to field of a PM in this forum? it pops up in another window and your action there is sent to the original window to add that member as a recipient of the message.
1.4.3.1
New: Force arrows to be selectable after loading (avoid noobs complaining about disabled arrows)
New: Copy segment attributes (thanks to bedo2991 & Zannax)
It seems there is still an occasional bug in the suppress unneeded junctions (on same endpoint fixes).
Can you reproduce this one?
Looks like when both nodes of the “same-endpoint-loop” segments have multiple segments connected to it, something strange happens.