Opened 14 years ago

Closed 14 years ago

#2859 closed patch (fixed)

symbology: unique value/categorized -> allow data driven labels

Reported by: lutra Owned by: mhugent
Priority: minor: annoyance Milestone: Version 1.6.0
Component: Symbology Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

it would be really useful to allow users define labels using the values of a column in the table of attributes.

It would be also useful to allow data driven symbol color RGB values.

Attachments (1)

100724_qgis_label.diff (79.7 KB ) - added by mhugent 14 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 by lutra, 14 years ago

Summary: symbology: unique values/categorized -> allow data driven labelssymbology: unique value/categorized -> allow data driven labels

comment:2 by lutra, 14 years ago

Version: Trunk

comment:3 by mhugent, 14 years ago

Owner: changed from nobody to mhugent

I'm currently working on data dependent labelling-ng (data dependent RGB values is something different. Probably it should be a ticket on its own)

by mhugent, 14 years ago

Attachment: 100724_qgis_label.diff added

comment:4 by mhugent, 14 years ago

Owner: changed from mhugent to wonder
Type: enhancementpatch

The attached patch adds support for data defined font and buffer settings to the new labeling. Martin, could you review it?

Thanks, Marco

comment:5 by wonder, 14 years ago

Owner: changed from wonder to mhugent

Marco, I've checked the patch and it looks fine.

I would also remove the legacy prepareLayer() call as I don't think we need to care about backwards compatibility here (labeling-ng is the only user of that interface). Additionally, I would use QList<in> instead of QSet<int> for the list of attribute indexes - a list is used also when passing the indexes to layer/provider.

comment:6 by mhugent, 14 years ago

Resolution: fixed
Status: newclosed

Applied in r13998. Thanks for reviewing, Martin. I removed the legacy method but kept the QSet (it is a bit easier for the label engine to filter duplicated fields).

Note: See TracTickets for help on using tickets.