Opened 13 years ago
Closed 13 years ago
#7864 closed defect (fixed)
Some primitives drawn in active color when the layer is inactive
Reported by: | mrwojo | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | inactive | Cc: |
Description (last modified by )
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)
follow-ups: 2 4 comment:1 by , 13 years ago
comment:2 by , 13 years ago
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 by , 13 years ago
Description: | modified (diff) |
---|
by , 13 years ago
Attachment: | InactiveSelectionColor.patch added |
---|
comment:4 by , 13 years ago
comment:6 by , 13 years ago
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.
follow-up: 8 comment:7 by , 13 years ago
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 by , 13 years ago
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 by , 13 years ago
Summary: | [Patch] Some primitives drawn in active color when the layer is inactive → Some primitives drawn in active color when the layer is inactive |
---|
Replying to mrwojo:
Would be nice if it is only the colour. Last time I checked it was quite worse: #6518 and #6447.