Opened 16 years ago

Closed 15 years ago

#921 closed enhancement (wontfix)

Feature: Carry single symbol settings over to other 'Legend type' settings

Reported by: jctull Owned by: nobody
Priority: minor: annoyance Milestone: Version 1.0.3
Component: Symbology Version: Trunk
Keywords: legend, symbol, classification Cc: pcav
Must Fix for Release: No Platform: All
Platform Version: All Awaiting user input: yes

Description

One big hassle is changing settings for unique value legends for datasets with many classification variables. The default action of line outline style is sometimes not wanted, and going through each classification value is tedious. It would be useful if Qgis carried over the settings made in Single Symbol when choosing a different legend type. For instance, setting the single symbol legend to 'no pen' will carry over as the default outline style when choosing 'unique value' classification, thus preventing the need to go through each class to change the outline style. The same could be done with width and fill style.

Change History (3)

comment:1 by lutra, 15 years ago

Cc: pcav added

It is possible, when classifying, to choose at the same time how many classes you want by using the SHIFT/CTRL keys + up/down arrow or pageup/pagedown keys or left mouse button, exactly the same way is done for files in a folder. Then, you can change the classification style for how many classes do you want at the same time.

This answer your question?

comment:2 by jef, 15 years ago

Awaiting user input: set

comment:3 by jctull, 15 years ago

Resolution: wontfix
Status: newclosed

@pcav I recognize that you can do what you have described. What I was suggesting is having qgis set the classified values to "no pen" outline styles if the single symbol style is already set to no pen. Likewise, have them dashed if the single symbol value is already set to dashed for the outline drawing. This is not a big deal now that you can select multiple items and set the outline style simultaneously, so I am closing this request as it has little value IMO. I'll classify it as wontfix.

Note: See TracTickets for help on using tickets.