Modify ↓

Opened 13 months ago

Last modified 13 months ago

#7681 new defect

not all relation gaps are detected

Reported by: NE2 Owned by: team
Priority: normal Component: Core
Version: Keywords: relation jump gap
Cc:

Description (last modified by skyper)

The previous/next gap doesn't find one that looks like this:

  |
 /
|
|
|
    |
    |
    |
  |

Note the lack of angle at the bottom of the right side. This happens when the left side is missing its last element.

Attachments (1)

temp.osm​ (3.4 KB) - added by NE2 13 months ago.

Download all attachments as: .zip

Change History (6)

comment:2 Changed 13 months ago by skyper

  • Description modified (diff)

comment:3 Changed 13 months ago by skyper

  • Description modified (diff)

comment:4 in reply to: ↑ description Changed 13 months ago by skyper

  • Keywords relation jump gap added
  • Owner changed from team to NE2
  • Status changed from new to needinfo

Replying to NE2:

Note the lack of angle at the bottom of the right side. This happens when the left side is missing its last element.

Please, add an example file as it is much easier to test and fix this bug with a test file.

Is it right that the part is missing on the left side or did you mix up the sides ?

Changed 13 months ago by NE2

comment:5 Changed 13 months ago by NE2

  • Owner changed from NE2 to team
  • Status changed from needinfo to new

comment:6 Changed 13 months ago by NE2

Yes, it is the left side. Example uploaded.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team. Next status will be 'new'.
Next status will be 'needinfo'.The owner will change to NE2
as duplicate The resolution will be set to duplicate. Next status will be 'closed'.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'.
Author


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

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.