* [processing] Fix atlas export relying on predefined scale for atlas-controlled map items
* De-duplicate code, add a QgsLayoutUtils::predefinedScale function
For same reason as we do in Processing registry:
(from the comments included in this commit)
"
While it seems like /Factory/ would be the correct annotations here, that's not
the case.
As per Phil Thomson's advice on https://www.riverbankcomputing.com/pipermail/pyqt/2017-July/039450.html:
"
/Factory/ is used when the instance returned is guaranteed to be new to Python.
In this case it isn't because it has already been seen when being returned by QgsProcessingAlgorithm::createInstance()
(However for a different sub-class implemented in C++ then it would be the first time it was seen
by Python so the /Factory/ on create() would be correct.)
You might try using /TransferBack/ on create() instead - that might be the best compromise.
"
are to be clipped from the project, instead of just tracking this
by the presence of any checked layers
Avoids inconsistencies between the layers which are visibly clipped
on the map vs the options which are set in the GUI.
individual table cells in manual text tables
Allows users to set the text horizontal and vertical alignments
on a cell by cell/column/row basis
Sponsored by City of Canning
Individual cells (or selections of multiple cells) can have an preset
text format set, which overrides the default text format for those cells.
Sponsored by City of Canning
method when exporting layouts to PDF
Options are for Lossy compression, which is the default JPEG compression
used, and Lossless compression (which creates bigger files in most
cases, but is much more suitable for professional printing outputs
or for post-production in Illustrator/etc)
The Bad news: this option is available in builds based on Qt 5.14
or later.
This feature allows users to enable map clipping for layout map items
so that the maps are clipped to the boundary of the current atlas feature.
(It's available for polygon atlas coverage layers only, for obvious reasons!)
Options exist for:
- Enabling or disabling the clipping on a per-map basis
- Specifying the clipping type:
- "Clip During Render Only": applies a painter based clip, so that
portions of vector features which sit outside the atlas feature become
invisible
- "Clip Feature Before Render": applies the clip before rendering features,
so borders of features which fall partially outside the atlas feature
will still be visible on the boundary of the atlas feature
- "Render Intersecting Features Unchanged": just renders all features
which intersect the current atlas feature, but without clipping their
geometry
- Controlling whether labels should be forced placed inside the atlas feature,
or whether they may be placed outside the feature
- Restricting the clip to a subset of the layers in the project, so that
only some are clipped
Sponsored by City of Canning
files for each logical layer in a layout
The backend for this was previously used only when creating a GeoPDF
export, where we create an individual PDF per layout logical layer
which are then composited by GDAL.
By publicly exposing this functionality via the QgsLayoutExporter API
we allow for plugins which can export layouts to seperate logical
PDF files, allowing for other (non-GDAL) tools to be used to later
composite the layers (e.g. Adobe Illustrator (which stupidly cannot
handle multi-layer single PDF files!))
Sponsored by SMEC/SJ
