QGIS/python at 2cf9243edbec4d5dce82e4e7d86437d1c306fb2c - QGIS

mirror of https://github.com/qgis/QGIS.git synced 2025-04-17 00:04:02 -04:00

History

Matthias Kuhn 2cf9243edb Split displayField into displayExpression and mapTipTemplate (#1973 )

Previously there was the expressionField (a field name or an expression)
mainly used for the feature list in the form view of the dual view.
On the other hand there was the displayField which could contain either
a simple field name or a complex HTML structure with embedded expressions.
And to know what it was you could compare it's content with the field names, if
a field name matched, you used it as a displayField (original purpose) and
if not... well, you could deal with HTML if you had a use for it.

The main problem is that there are two different usages for this kind of
thing

 * plain text identifier (field or expression)
 * pretty, rich text feature info

This commit cleans up with this. You want rich text and a lot of info:
go for mapTipTemplate.
You want a plain text string to identify features: go for
the displayExpression.

2016-08-02 16:58:58 +02:00

analysis

Make all QgsGeometry methods return values, not pointers

2016-08-01 22:41:55 +10:00

console

Fix running unsaved script in console

2016-05-16 18:14:58 +10:00

core

Split displayField into displayExpression and mapTipTemplate (#1973 )

2016-08-02 16:58:58 +02:00

custom_widgets

Formatting update, using newer autopep8 version