671 Commits

Author SHA1 Message Date
Peter Petrik
33390123e3 various small fixes from review 2018-05-22 14:32:20 +02:00
Denis Rouzaud
c1e16969f3 [QgsLocator] add the capability of adding group for elements within the same filter 2018-05-17 21:46:31 -04:00
Denis Rouzaud
1a879b18a1
Merge pull request #7002 from 3nids/sip_metoobject
[sipify] insert missing QMetaObject for gadget classes
2018-05-16 17:54:06 -08:00
Nyall Dawson
5edcc64f72 [processing] Allow algorithms to return a translated short description
This is used in the algorithm's tooltip in the toolbox, and is intended
for single sentence description of the algorithm, e.g.
"Converts 2D features to 3D by sampling a DEM raster."

Convert grass algorithms to use short description for the
descriptive parts of their names, to cleanup the toolbox
and make it more uniform.
2018-05-17 08:50:39 +10:00
Martin Dobias
94f56b61a8 Build/test fixes 2018-05-16 17:26:59 -04:00
Denis Rouzaud
2abcfa23b8 do not add static QMetaObject to QgsDefaultValue
it has no Q_ENUM so no need for now
I do not understand while it doesn't compile though
2018-05-16 14:25:01 -04:00
Peter Petrik
3fc99c04c1 code cleanup 2018-05-16 17:02:35 +02:00
Denis Rouzaud
5790bbcad6 fix QgsAbstractGeometry Q_GADGET position 2018-05-16 07:54:17 -04:00
Peter Petrik
aea3dccea7 [FEATURE] Rendering of vector data on mesh layers
Rudimentary support of rendering of vector data (e.g. velocity) on mesh map layers.
Rendering can be adjusted by QgsMeshRenderer*Settings. Only in Python
API, no GUI widgets for styling present.
2018-05-16 12:56:35 +02:00
Martin Dobias
9296528822 [FEATURE] Rendering of scalar data on mesh layers
Rudimentary support for rendering of scalar data (e.g. water depth)
on mesh map layers.
2018-05-16 12:47:57 +02:00
Peter Petrik
3154102aa6 [FEATURE] Scalar/vector data in mesh data providers
Reading and processing scalar (e.g. water depth) and vector (e.g.
velocity) data from mesh data providers (e.g. MDAL)
2018-05-16 12:47:28 +02:00
Alessandro Pasotti
a44eeae441
Merge pull request #6982 from elpaso/currentformfeature-expressions-4
[feature][need-docs] Current feature/current value form context expressions
2018-05-16 09:48:06 +02:00
Nyall Dawson
6c02d0534a Super-basic title-case conversion method
No grammatical parsing, so only useful for very simple cases
2018-05-16 14:08:43 +10:00
Denis Rouzaud
e8cf8c2f1c [sipify] insert missing QMetaObject for gadget classes 2018-05-15 17:38:16 -04:00
Nyall Dawson
c9e5a36558 [processing] Avoid generic exceptions
Makes the full Python exception available when running algorithm,
which provides much more useful error messages
2018-05-16 04:35:17 +10:00
Alessandro Pasotti
673fac0c88 Added methods to search expression nodes and drop RegExp
- nodes() return the list of all nodes
- findNodes<T> returns a list of the nodes matching the class

Also drops the regexp for finding form attrs in the value-relation
expressions.

Other minor fixes as suggested in the PR review.
2018-05-15 18:32:40 +02:00
Alessandro Pasotti
b4f86147c7 Add referencedFunctions() to expressions 2018-05-15 09:20:10 +02:00
Alessandro Pasotti
541737681b Moved form feature to private and added setters/getters
plus other minor style changes as suggested by m-kuhn
in his PR review
2018-05-15 08:34:08 +02:00
Alessandro Pasotti
83328ae596 [feature] Form context expressions in value relation widget
The value relation widget filter expression can now use two
new functions/variables that have access to the current
values and geometry of the form being edited.

This allows for dynamic filtering (drill-down) as explained
in the crowdfunding page:
https://north-road.com/drill-down-cascading-forms/

The new functions/variables are:

Function:
get_current_form_field_value( 'FIELD_NAME' )

Variable:
@current_form_geometry
2018-05-15 08:34:08 +02:00
Denis Rouzaud
fca72fa7d1 put back module sip files 2018-05-14 11:02:28 -04:00
Denis Rouzaud
7df2593caf move auto generated sip file in dedicated folder 2018-05-14 10:23:37 -04:00