to improve performance (actually to make it usable with large tables again).
When used as initial setting in options the open attribute table will have a
fixed spatial filter to the canvas extent when it was opened. That extent is
also highlighted to indicate the filter.
fixes#10619
* support edit types based on edit widgets (adds qgis_gui dependency; fixes#12091)
* show null values (fixes#12114)
* only quote non-numeric non-null values in feature info
* fix crash on exit
* remove obsolete parser method and debug output
Make sure image dpi respects mapsettings dpi in
QgsMapRendererSequentialJob.
Also apply a workaround to avoid segfault on end of test. This
workaround probably should be moved to QgsApplication::exitQgis()
but I'll do that after release in case of regressions.
- Switch STREQUAL conditionals to MATCHES for Clang to handle CMake 3
introduction of AppleClang compiler ID for Mac-specific Xcode clang,
which has different reported versions than upstream clang
These failing tests are actually revealing an issue with the atlas
map API, which can't be fixed without a break.
This API will be replaced for QGIS3.0 or the layout refactor work.
This test checks that the coverage of the API docs does not drop
below a preset threshold (initially set at the current doc coverage)
If new members are added without documentation, then the coverage
will drop and this test will fail. Hopefully over time we can slowly
increase this threshold until documentation coverage reaches an
acceptable level.
In field calc opened from attribute table, when changing attributes
there is a series of signals: layer emits attributeValueChanged(),
cache forces update of attribute table data, which at one point calls
layer.isModified(), emitting beforeModifiedCheck() - in turn calling
save() of attribute form, which would change first feature's new attribute
to a bogus value. This recursive change of attribute values corrupts
the undo stack.
The fix pre-sets the feature's attribute so that no dummy entry is
added to the undo stack.
In the future we should probably try to improve the whole cascade
to avoid bugs like this one:
1. if possible, make emission of edit signals "safe", so a slot can
do more editing calls without corrupting undo stack
2. get rid of beforeModifiedCheck() signal as it adds quite surprising
behavior (and overhead) to what should be a simple check
