Modify

Opened 4 years ago

Closed 4 years ago

#3328 closed defect (fixed)

show note= again at relations

Reported by: malenki Owned by: team
Priority: normal Component: Core
Version: latest Keywords:
Cc:

Description

At the relationlist up to some not so old versions one was showed the name of the raltion and if nonexistend the contend of the note-field. Now that behaviour is changed into showing the relation-ID if no name is present.
I want the old behaviour back. It is not useful start tagging hikingroutes with name=red bar which i found between city A and village B.
How is one supposed to tell the routes apart from each other? Surely not by learning all the IDs inside out. At the moment I edit a one days 55 km-log. The date I downloaded along contains about 54 relations of which 33 are routes. Enhancing hiking routes (which whas the main reason i spent my holidays for OSM) is impossible at the moment so please fix that quick.

java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode)

josm 1992

Attachments (1)

josm_one_relation_without_note.png (94.2 KB) - added by malenki 4 years ago.

Download all attachments as: .zip

Change History (16)

comment:1 follow-up: Changed 4 years ago by anonymous

  • Priority changed from critical to normal

This is not really critical. Setting to normal.

comment:2 Changed 4 years ago by Gubaer

  • Resolution set to fixed
  • Status changed from new to closed

(In [1997]) fixed #3328: show note= again at relations

comment:3 in reply to: ↑ 1 Changed 4 years ago by anonymous

Replying to anonymous:

This is not really critical. Setting to normal.

... but I fixed it anyway :-)

comment:4 Changed 4 years ago by Ldp

This is a duplicate of #1747 that was reopened *yesterday*. Funny thing, new tickets attract more attention than reopens of old tickets. I'll remember that.

comment:5 Changed 4 years ago by anonymous

Oh, I didn't yet scroll down to #1747 ;-) Now, it's closed too.

comment:6 follow-up: Changed 4 years ago by malenki

It was critical to me since I could not continue working at "my" hiking routes. Indeed it would have been blocker for me, if there wouldn't be a "tested" JOSM. ;)

Sorry I did not find 1747. I admit this time i had forgotten to search for an existing ticket.

And I want to thank you for the fast fixing!

Regards
malenki

comment:7 Changed 4 years ago by Ldp

Malenki, you can always step back to an earlier 'latest' as well:

http://josm.openstreetmap.de/download/

comment:8 in reply to: ↑ 6 Changed 4 years ago by anonymous

And I want to thank you for the fast fixing!

I had to, it was me who broke it ;-)

comment:9 Changed 4 years ago by malenki

  • Resolution fixed deleted
  • Status changed from closed to reopened

anonymous broke it? I hope anonymous will fix it again since it's broken in 2091 again.

comment:10 Changed 4 years ago by Gubaer

Can't reproduced. I tried the following steps:

# create new relation
# add just one tag: note=This is a note

The relation is then displayed with the name relation("This is a note"), 0 elements) in the relation list dialog.

Do you have more specific infos about what is going wrong?

comment:11 Changed 4 years ago by malenki

  • Resolution set to fixed
  • Status changed from reopened to closed

Sorry, my failure this time. I mixed up a relation which had indeed no note with another one with the same amount of elements :(

comment:12 Changed 4 years ago by malenki

  • Resolution fixed deleted
  • Status changed from closed to reopened

I am sorry to reopen this again, but I found one relation whose note is not - unlike all others - displayed. Strange thing. The relation is # 239129, see also the screenshot.

Changed 4 years ago by malenki

comment:13 Changed 4 years ago by Gubaer

The tag key is note (with a trailing blank).

Could qualify as a "data error" but I guess I'd better fix it in the code (checking for "note" tags with whathever-sequence-of-trailing-or-leading-whitespace) ;-)

comment:14 Changed 4 years ago by malenki

arghs -.- And I thought I checked everything.
sigh

Thanks for letting me bother you. ;)

comment:15 Changed 4 years ago by Gubaer

  • Resolution set to fixed
  • Status changed from reopened to closed

fixed in r2136

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.