Opened 14 years ago
Closed 14 years ago
#5570 closed enhancement (fixed)
[PATCH] Brightness/transparency of WMS layer control
Reported by: | jekhor | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core imagery | Version: | |
Keywords: | Cc: | Upliner |
Description (last modified by )
Sometimes WMS layers are too bright and this makes map data layers almost unreadable. Some kind of control WMS layer brightness or transparency will be useful.
Attachments (4)
Change History (18)
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
Summary: | Brightness/transparency of WMS layer control → [PATCH] Brightness/transparency of WMS layer control |
---|
follow-up: 5 comment:4 by , 14 years ago
Technically it looks good, but we should improve the GUI a little. My idea would be to merge it somehow with the visibility switch ("eye") because it's a special case of transparency (0% and 100%).
Then some visual feedback would be good. Currently it shows a red cross on the layer icon for 100% transparency. Maybe we can come up with some gradual display?
comment:5 by , 14 years ago
Replying to bastiK:
Technically it looks good, but we should improve the GUI a little.
Yes, I should at least draw an icon for new button.
My idea would be to merge it somehow with the visibility switch ("eye") because it's a special case of transparency (0% and 100%).
How do you see it? If you offer something specific, I'll do it.
comment:6 by , 14 years ago
Sorry it took so long to answer. I have a bigger change in mind and haven't found time to do a prototype, yet. The basic idea is to make the list entry symbols clickable like in gimp image software. Then you can add a transparency slider button next to the eye button field. We could have an extra column for active layer at the left, so the importance of "active layer" is more clear.
comment:7 by , 14 years ago
Ok, I did the changes I had in mind ([3661]).
- My suggestion would be to (practically) remove the
visible
field fromLayer.java
. A layer is invisible when the opacity value is 0 and it is opaque when this value is 1. - A click on show/hide changes the opacity value to 1 in case it is < 1 and to 0 otherwise.
- It should be clearly (and directly) visible, whether a layer is opaque, or just 99% visible. (Because there is a considerable performance loss for half-transparent layers.)
- The easiest way would be to change the new "eye" symbol in the layer list depending on the opacity value:
- invisible and opaque like it is now.
- another symbol that represents all opacity values > 0 and < 1. (E.g. the "eye" symbol, but half transparent.)
by , 14 years ago
Attachment: | transparency.png added |
---|
Created an icon. Not too good, but maybe its a start...
comment:8 by , 14 years ago
Cc: | added |
---|
I'm sorry for long response too... I don't want remove the visible
field because current implementation has a nice feature: it remembers opacity level for hidden layers. I.e I can hide a half-transparent layer and then show it again with same transparency level. I't exteamly convenient for me when viewing the OSM tiles over the Bing imagery. Clicking at eye icon is much easier than moving a slider.
comment:9 by , 14 years ago
I see your point. I'd like to show some symbol in the corresponding line of the layer list, whenever the opacity is different from 100%. Any ideas?
comment:10 by , 14 years ago
Maybe just show a half-transparent dithered eye icon like that? I know that dithering is kind-of out of fashion, I just don't have an another idea...
comment:11 by , 14 years ago
ok, this will get in after next release, i'll come up with something...
follow-up: 13 comment:12 by , 14 years ago
Problem with the half transparent eye: User is used to toggle sequence: closed, open, closed, open, ...
now he/she changes transparency and it is: blurred, closed, blurred, closed, ...
so the question would come, how do i get it back to 100% opaque? (Right, move transparency slider to 100%)
comment:13 by , 14 years ago
Replying to bastiK:
Problem with the half transparent eye: User is used to toggle sequence: closed, open, closed, open, ...
I don't see a big problem here. If user already have moved a slider why he can't move it again? I think it's a situation where any solutions would have some drawbacks...
My solution seems to be quite efficient: transparency is often used for imagery layers and user usually don't need more than one fully opaque imagery layer, however he/she might want to temorary disable some of half-transparent layers.
by , 14 years ago
Attachment: | opacity.diff added |
---|
I wrote a patch that allows to change opacity of any layer