Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#4279 closed defect (worksforme)

Untagged nodes now appear as tagged nodes

Reported by: Ldp Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:


Since 2722, untagged nodes show up the same as tagged nodes previously did. That is, as a hollow square. This means a map of untagged nodes now shows up as a sea of large yellow dots, instead of the small dots they had before.

If I tag a node, it appears even larger than a tagged node did before.

Attachments (2)

gkrellShoot_2010-01-02_152201_josm_2725_big_nodes.png (205.7 KB) - added by malenki 11 years ago.
Josm 2725 (big nodes)
gkrellShoot_2010-01-02_152214_josm_2721_small_nodes.png (206.1 KB) - added by malenki 11 years ago.
Josm 2721 (small nodes)

Download all attachments as: .zip

Change History (11)

comment:1 Changed 11 years ago by stoecker

Resolution: fixed
Status: newclosed

(In [2725]) close #4279 - use previous node size defaults

comment:2 Changed 11 years ago by Ldp

Resolution: fixed
Status: closedreopened

It hasn't helped. Tried it with 2725*, with and without preferences file, so the latter one with a plain JOSM. I still have the hollow node appearance.

  • ant clean build

comment:3 Changed 11 years ago by malenki

The commit-comment in is "close #4279 - use previous node size defaults"

Comparing Josm 2721 to 2725 shows that the latter displays tagged and empty nodes not in the same way 2721 does.

Changed 11 years ago by malenki

Josm 2725 (big nodes)

Changed 11 years ago by malenki

Josm 2721 (small nodes)

comment:5 Changed 11 years ago by stoecker

Resolution: worksforme
Status: reopenedclosed

The current setup is a solution which works on small and large screens. You can change them yourself. Go to advanced settings and search for node and size.

comment:6 Changed 11 years ago by malenki

Is this what "pulling a Drepper" describes, is it?
"Go on, all Josm users and change your advanced settings if you want the old behaviour back."

Thank you so very much.

comment:7 Changed 11 years ago by stoecker

Sorry, but we can't make every individual happy. We have 20 year old mappers as well as 70 year old mappers. The previous default (which was inconsistent and needed a fix) was much too less for a 70 year old an a recent screen resolution. Details of the software change, this is normal behaviour. If you don't accept changes and if you don't want to accept the possibility to change it for yourself, then don't update the software!

EVERY user finds that HIS settings are the best and should be standard. This is usually not true. I doubt most users want to change the dot size, so this will remain a hidden option. For you this seems important so go to advanced settings and change it there. But stop blaming others for having different opinions.

comment:8 Changed 11 years ago by malenki

You write

I doubt most users want to change the dot size

but you don't doubt they want others changing the dot size for them?

I don't think I am the only person with the opinion expressed above. More exactly: I know this.

comment:9 Changed 11 years ago by Ldp

As this is a major appearance change to most users, then at least put it up on the MOTD, with hints on how to change back.

You cite 70 year old mappers (or mappers in general with bad eye sight and high resolution screens) as the reason for making the nodes appear larger. Fair enough. Let me make another observation, as a person that's reasonable well trained to spot deviations from patterns. Previously, the distinction between tagged and untagged nodes was an open (hollowed) appearance, vs a closed dot. Now they're all open, but only vary slightly in size, which is harder to spot. Could you give some thought on keeping the open vs closed dot appearance, at least as a configurable option?

Modify Ticket

Change Properties
Set your email in Preferences
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.