Feature request #3498
Add a flag "Label only selected features"
Status: | Open | ||
---|---|---|---|
Priority: | Low | ||
Assignee: | - | ||
Category: | Labelling | ||
Pull Request or Patch supplied: | No | Resolution: | |
Easy fix?: | No | Copied to github as #: | 13558 |
Description
It would be useful to add such a flag; currently this can be done with several workarounds, but all of them are rather ugly
History
#1 Updated by Paolo Cavallini over 13 years ago
This only for new labeling system
#2 Updated by Giovanni Manghi almost 13 years ago
- Target version changed from Version 1.7.0 to Version 1.7.4
#3 Updated by Giovanni Manghi over 12 years ago
- Target version changed from Version 1.7.4 to Version 2.0.0
#4 Updated by Giovanni Manghi over 12 years ago
- Pull Request or Patch supplied set to No
- Assignee deleted (
nobody -) - Category changed from Symbology to Labelling
#5 Updated by Larry Shaffer about 12 years ago
Have a look at:
2fbc98e66f62a3c1324654a5957258ed29849f44
and
3dd05e6842757a8e466375ac062aefb072b09d9c
While not the same as 'only selected,' possibly better than the previous workarounds.
#6 Updated by Regis Haubourg about 12 years ago
I think 'label selected only' option is a great option, different from pin/unpin tools, since the last one requires advanced fields, and then possibility to modify or duplicate dataset.. Users often can't do that. It remains a tools dedicated to heavy labeling for me. A fantastic one of course ;-)
The only thing is that there is no way to save selection in a QGS project, correct me if i'm wrong. "label only selected" tool without ability to save it sounds quite useless to me, or at least dedicated to throwable work.
Implementing selection persistence in QGS can be really tricky. This is an unsolvable issue with Mapinfo, full of caveats..
I would rather spend efforts on refactoring labeling so that labels could be placed into layer order control dialog. That way, we could easyly generate masks (plugin Mask for example) and put labels under it.. How does that sounds to you?
#7 Updated by Pirmin Kalberer about 12 years ago
- Target version changed from Version 2.0.0 to Future Release - Nice to have
#8 Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#9 Updated by Paolo Cavallini almost 7 years ago
Still unimplemented in QGIS3