for transformation between a source and destination CRS pair should
permit falling back to a ballpark transform when required
This defaults to true (i.e. similar-ish behavior to proj 4), but allows
users who require a specific coordinate operation the ability to prevent
any fallback ballpark transformations occurring
for a particular QgsCoordinateTransform object
This can be set for transforms where we definitively know that a "ballpark"
result is acceptable, e.g. when transforming global layer extents to
a localized area-of-use CRS
Refs #33929
* drag'n'drop improvements
part 3
this completely removes hidden config accessible under double click
now a widget groupbox (by opposition to the field config) is shown on top of the right panel
Instead of hiding this functionality from users, we instead add an explicit
toggle to the Table Designer dialog "Table" menu to hide or show
the header cells in the designer, and re-add the widgets which
allow users to customise the header appearance back into the
item configuration widget.
Whenever a header cell is selected in the table designer, the formatting
widgets are disabled since the item's header configuration widgets
are used to set the background/foreground color and other properties
of these cells instead.
A new menu entry (Actions on selection) is added to the layer tree context menu
It is shown only when required (layer has selection and actions can be run on the given layer)
On touch screen devices, we can't show the GPS distance status bar message
as the cursor moves (because there's no "hover" mouse move events to trigger
this from). So for these devices, use a tap-and-hold event to trigger the
"current GPS distance from finger" status bar message.
of a layer or project is unknown
Because:
1. It clearly indicates that the current CRS for the object is unknown
2. It lets users see the full WKT/proj definition of the CRS, and allows
them to copy this definition
3. Avoids loss of CRS information when just opening and accepting the dialog
Refs #33458
- Make the new Temp Folder setting optional, default to an empty
string, and note that empty = use default
- Move responsibility for cleanup of temporary folders to c++ (if
Processing Python part crashes, or doesn't exist, then we still
want these cleaned up correctly)
model designer, prefer to show the user's defined name for that output
instead of the generic one
Makes it easier to associate inputs with the correct outputs when
creating models
