Modify

Opened 2 years ago

Closed 23 months ago

Last modified 23 months ago

#14708 closed defect (fixed)

no warning about potentially erroneous movement of existing nodes

Reported by: Don-vip Owned by: team
Priority: normal Milestone: 17.04
Component: Core Version:
Keywords: Cc: planemad

Description

from 11405 comments:

The warning works on newly created geometries but does not show up when moving the node for an existing object.

https://cloud.githubusercontent.com/assets/126868/25421121/f5ea3e0a-2a78-11e7-96ba-16587deacb5c.gif

Attachments (1)

patch-14708.patch (4.4 KB) - added by michael2402 23 months ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 23 months ago by Don-vip

Resolution: fixed
Status: newclosed

In 12032/josm:

fix #14708 - no warning about potentially erroneous movement of existing nodes

Changed 23 months ago by michael2402

Attachment: patch-14708.patch added

comment:2 Changed 23 months ago by michael2402

You were faster than me.

I added a test for the way segment to highlight the exact segment that causes the problem. I'll merge it after the release.

comment:3 Changed 23 months ago by Don-vip

You can merge it, I'll do the release after the i18n update.

comment:4 Changed 23 months ago by michael2402

In 12037/josm:

See #14708: For long segment test, notify the user about the exact segment. Do not check segments that have not been touched.

comment:5 Changed 23 months ago by michael2402

Zoom to problem now works by zooming to the right way segment ;-).

Only disadvantage: You get a warning for each way segment. They are grouped by segment length, not by way, so when working with a lot of ways that contain long segment (borders, ...), you might get a lot of messages. But people working there hopefully know what they are doing.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.