Opened 10 months ago
Closed 9 months ago
#7864 closed defect (fixed)
Some primitives drawn in active color when the layer is inactive
| Reported by: | mrwojo | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Component: | Core |
| Version: | latest | Keywords: | inactive |
| Cc: |
Description (last modified by mrwojo)
Swapping between two layers I noticed 3 4 minor cases where primitives are using their active color while the layer is inactive:
- Node icon selection border. Repro: Select a highway=stop node. Switch to a different layer. Stop icon remains bordered by red selection rectangle. I'd expect either the rectangle to be rendered in gray or not rendered.
- Area fill color. Repro: Find an area way with a fill color. Switch to a different layer. Area fill color remains as it was (it's easier to see the dark red fill of a selected area). I'd expect the area fill to be either gray or omitted.
- Turn restriction icon selection border. Repro: Select a turn restriction relation. Switch to different layer. Turn restriction icon remains bordered by pink selection rectangle. Again, I'd expect the rectangle to be either gray or omitted.
- Area text. Repro: Find an area with a displayed name. Switch to a different layer. The name text remains white-ish when it should be gray.
The attached patch does:
- Inactive node icon selection: Gray.
- Inactive area fill: Omitted. (This what's done for disabled areas. See StyledMapRenderer.java, line 118.)
- Inactive restriction icon selection: Gray.
- Inactive area text: Gray.
Attachments (1)
Change History (11)
comment:1 in reply to: ↑ description ; follow-ups: ↓ 2 ↓ 4 Changed 10 months ago by skyper
comment:2 in reply to: ↑ 1 Changed 10 months ago by skyper
Replying to skyper:
Replying to mrwojo:
Swapping between two layers I noticed 3 minor cases where primitives are using their active color while the layer is inactive:
Would be nice if it is only the colour. Last time I checked it was quite worse: #6518 and #6447.
Did run a quick check and I am able to move objects in inactive layers in all three cases:
- download same object twice in different layers
- select object
- switch layer
- select object
- move object
- switch layer
- move object -> object in inactive layer is moved.
Guess the problem is a bit deeper.
comment:3 Changed 10 months ago by mrwojo
- Description modified (diff)
Changed 10 months ago by mrwojo
comment:4 in reply to: ↑ 1 Changed 10 months ago by mrwojo
comment:5 Changed 10 months ago by Don-vip
In 5348/josm:
comment:6 Changed 10 months ago by Don-vip
Thanks for the patch.
I have integrated the points 1, 3 and 4, they were obviously bugs. Concerning the point 2, I see it as a quite fundamental change in inactive layers rendering as areas cannot be distinguished anymore.
I don't know if it's a good idea or not and would like to hear other opinions from team members.
comment:7 follow-up: ↓ 8 Changed 10 months ago by mrwojo
Another possibility would be to change the fill to inactiveColor with some reasonable alpha value (the default fill alpha of 50 with dark gray isn't typically visible).
comment:8 in reply to: ↑ 7 Changed 10 months ago by bastiK
Replying to mrwojo:
Another possibility would be to change the fill to inactiveColor with some reasonable alpha value (the default fill alpha of 50 with dark gray isn't typically visible).
+1, basically desaturating the colors for inactive areas would be an improvement.
comment:9 Changed 10 months ago by bastiK
- Summary changed from [Patch] Some primitives drawn in active color when the layer is inactive to Some primitives drawn in active color when the layer is inactive
comment:10 Changed 9 months ago by Don-vip
- Resolution set to fixed
- Status changed from new to closed
In 5431/josm:



Replying to mrwojo:
Would be nice if it is only the colour. Last time I checked it was quite worse: #6518 and #6447.