Allows users to override the line placement settings (e.g.
above/below/on line options) on a per-feature basis. Somehow
this one was the only(?) setting from labeling which
was missing a data defined control...
- grass data item provider fixes
- removed QgsProviderMetadata constructor (with std::function / PyObject) due to sip errors (api break)
- reverted DataCapability move to Qgis - back to QgsDataProvider (avoiding api breaks)
- WidgetMode enum documentation
- sipify monkey patching fix
- renamed WidgetMode's "None" to "Normal" value - in python None has special meaning (api break)
This accomplishes several things:
- Offers an indication to user that there are layer-related actions
- Single click access to contextual menu
- Offers an indication to user where layers are located when viewport is
horizontally scrolled to right, and layer names are not visible
Since last column is resized to content (instead of stretched), the
active selection rectangle ends at width of widest visible item in tree,
regardless of which item is selected. This causes layer indicators to
become 'inactive' (not clickable and no tool tip) unless their rectangle
enters the view item's selection (active) rectangle. Always resetting
the minimum section size relative to the viewport ensures the view
item's selection rectangle extends to the right edge of the viewport,
which allows indicators to become active again.
And:
- fix enable state of selected features only after changing between
map layers with/without selections
- fix state of selected features only when running an algorithm
from the history list, e.g. respect original setting for
selected features only (or not)
- ensure no duplicate changed signals are sent, and correctly
emit changed signals in all applicable circumstances
- handle drag and dropped layers from browser panel (UX fix)
- soak with unit tests
These methods either
- only wrap QSettings values (so there's no added security gained
by not exposing them -- it's currently easily possible to achieve
the same results via direct QSettings manipulation)
OR
- are required to allow fully automated QGIS deployment/startup
scripts which rely on auth manager functionality
Include the input parameter values in the report, otherwise the
results are just a meaningless list of values which can't be
associated with any particular set of inputs
Also correctly handle boolean and other output types
