the QGIS application from exiting
This interface allows plugins to implement custom logic to determine whether it is safe
for the application to exit, e.g. by checking whether the plugin or script has any
unsaved changes which should be saved or discarded before allowing QGIS to exit.
This signal is emitted whenever the application options have been changed.
This signal is a "blanket" signal, and will be emitted whenever the options dialog
has been accepted regardless of whether or not individual settings are changed.
It is designed as a "last resort" fallback only, allowing widgets to respond
to possible settings changes.
to new "Code Editor" tab in options dialog
These settings apply to more than just the Python console editors -
rather they apply to all code editors across QGIS (including expression
editors)
Remove a bunch of duplicate default color definitions, and ensure
that all subclasses correctly respect any user defined color overrides,
yet that we still default to following the application theme's matching
color schemes.
Instead of the confusing duplicate settings for foreground color
vs cell text color, remove the foreground color button and only
expose this color setting via the cell text color.
* QgsField::ConfigurationFlags: use a negative form for the flags so that default flags is None
this will make this futureproof, so newly added flags won't cause trouble for compatibility with old projects
* follow up
* remove template class
* fix order of init
* follow up
* Revert "update test projects (open and save)"
This reverts commit c738609d9177ed398ba2a0ae0e1c16448accd5f6.
* DoNotExposeVia -> HideFrom
a locator filter can now return a completion list while preparing the search
the line edit will use the first matching completion and display it as light grey text
the completion can be triggered by pressing Tab key
buttons to combo box
The radio buttons don't work well here -- they cause a massive
gap in the placement UI layout for anything but polygon
layers. Using a combobox is also much more compact, giving us
some extra space to use for more helpful explanatory text
of labels along line features
The new "Label Anchoring" section in the line placement settings for
labels allows users to specify whether labels should be placed
at the center, start or end of lines (or a custom percent from the
start of the line). Also allows data-defined percent along line
control!
To not be needed to check for all the widget values in the form, the mCurrentFormFeature is introduced that contains all the values that are received on change of the widget values.
Resolves#37678
renamed cardinality to nmRelationId since it's not a cardinality - it's the id of the relation connected through the many-to-many cardinality in this relation editor widget
