[Script] WME Toolbox

[voludu2]

Thank you for all the fixes you have made so far.
I find I am completely or mostly unable to drag the floating tools around.
I tested this with Tampermonkey disabled and Toolbox as my only WME-related extension.

When I try to click-drag the floating toolbar, or the floating arrows tools, it might move a couple of pixles to the left or right, or not at all, and I wind up selecting text in one or more layers instead.

If I try this with other scripts on, I find I might select PIE-displayed place names or county names from another script.

Am I the only one having this problem?

[voludu2]

I sense this behavior, too. However, I can drag the controls if I move the mouse very slowly. It seems the drag status is lost if the mouse cursor moves too far away from the control, so the behavior might also be dependent on the performance of the computer you're working on. I'm not aware that we changed anything which could have caused this issue. But anyway, we'll investigate.

Thanks! I did some more checking, and here's what I found
1) If there is NOTHING on the screen, then I can hold down the left mouse button and drag the things around at a "normal speed", then everything is fine. The cursor might get ahead of the floating item, but there is no problem
2) The problem happens if the cursor (with the left mouse button pressed) passes over a segment while it is separated from the floating thing. The segment then "lights up" the way we expect it to do when hovering over a segment with no buttons pressed. Immediately, the action of the cursor changes from dragging the floating thing to selecting nearby text.

It seems to me that this change in behavior while dragging is the result in a change in how WME behaves when the cursor is being used to drag.

[voludu2]

Hi! I have noticed lately that "q" disables all u-turns at a node.
This seems like unwanted behavior when all I want to do is confirm all turns at the node.

Once upon a time, when waze team told us Waze could not handle these u-turns and we were to disable all u-turns, this made sense. But that was a long time ago.

I think it would make sense to change this behavior.

[voludu2]

I would support a toggle for the JNF "Q" to "do not change"(default) / "restrict all" u-turns at the node.
To my way of thinking, "do not change" is more consistent with what JNF-Q does to the other arrows at the node - confirm, but do not change.

I would support a toggle for the disable-U-turn function of JNF. However, I really think it should default off, because knowledgeable users will know to turn it off (once, after Toolbox is updated), but new users to JNF/Toolbox will not inadvertently delete sometimes-useful U turn information. We should default to data preservation where possible...

[walbing]

In my case i am level 5 and me were off, could you tell us who made the decision to Colombia? i do not use for mass editions, the use for consultations in Colombia are very few level 5 and would like to continue to have them and that what is done is to make a difference, now Level 5 are as adept as a level 6.

Thank you and hope promp response

[walbing]

In my case i am level 5 and me were off, could you tell us who made the decision to Colombia? i do not use for mass editions, the use for consultations in Colombia are very few level 5 and would like to continue to have them and that what is done is to make a difference, now Level 5 are as adept as a level 6.

Thank you and hope promp response

in your screenshots the select segment list appears to be working for you, what is the issue?

These are screen captures of old, but now no longer work for.

Tks

[walbing]

I think the same thing in Colombia happen many editors left because increasingly they are furthest from achieving goals of improving the maps this that makes seeing is discrimination others because for that we are the top level to take the right path, not it may be that a person in a contry who legislate if and who is not.

Just before taking a determinacion coodinators should ask others Chanps country.

Best Regards.

[walbing]

ok pesanchz , the problem is that mincho77 never consulted us the LC, so the discontent of the Colombian community.

Best regards

Enviado desde mi SM-T230 mediante Tapatalk

[walbing]

ok pesanchz , the problem is that mincho77 never consulted us the LC, so the discontent of the Colombian community.

Best regards

Enviado desde mi SM-T230 mediante Tapatalk

I understand your frustration, but you can't fix it here. You need to have a conversation with all the Columbian Champs to figure out the path forward.

Sent using Tapatalk for Android

ok thanks pesachZ. see you.

Enviado desde mi SM-T230 mediante Tapatalk

[wargollo]

I have this same problem in these versions:

59.0.3071.86 (Official) - 64 bits
60.0.3112.21 (DEV) - 64 bits