#1851 closed enhancement (worksforme)
symbology multiple selection should highlight all regardless of different properties
Reported by: | dassouki | Owned by: | nobody |
---|---|---|---|
Priority: | minor: annoyance | Milestone: | Version 1.2.0 |
Component: | Symbology | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
sometimes, a line layer can have 40 different classications; however, i'd like to have the first 20 to have a similar style (black line with pink brunsh for instance). When i multiple select the items in symbology, i can't change the color field. Thus, i have to change each classifaction's color on its own.
Is it possible to add a feature that allows for multiple highlighting and change the color / line type of all the highlighted features, regardless of the colors in them.
Change History (5)
follow-up: 4 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:3 by , 15 years ago
Resolution: | duplicate |
---|---|
Status: | closed → reopened |
Replying to dassouki:
sometimes, a line layer can have 40 different classications; however, i'd like to have the first 20 to have a similar style (black line with pink brunsh for instance). When i multiple select the items in symbology, i can't change the color field. Thus, i have to change each classifaction's color on its own.
Is it possible to add a feature that allows for multiple highlighting and change the color / line type of all the highlighted features, regardless of the colors in them.
You can only change properties that are common for all selected classes.
Inititially all properties except for the color are the same. That's why there is a possiblity to reset the color of all (selected) classes to white. That also opens the opportunity to change colors for multiple classes at once.
comment:4 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
It is a duplicated ticket, see #1703.