This reverts commit a475af2.

This reverts commit 3ec5104.

This reverts commit a57b827.

This reverts commit 7f0d5de.

This reverts commit ae087a3.

Python says no.

- remove protobuf-devel from explicit list - should be included in deps
- only use the extra #define where needed
- disable vector tile test on azure for now (can't debug it)

[FEATURE] Vector tile layer - part 1

for rendering

We can safely use ballpark transforms without bothering the user here --
at the likely scale of layer extents there won't be an appreciable
difference, and we aren't actually transforming any rendered points here
anyway (just the layer extent)

Fixes #34983

the widget directly to a scale from a print layout map

…cular

theme, then correctly follow that same theme's styling when rendering
the legend

Fixes layout legends always render using the canvas' visible theme styling,
instead of that of the linked map.

Fixes #27542, #24694, #28919, #28925

Fix sponsored by the Victorian Planning Authority

[FEATURE] Use temporal controller for the mesh layer time handling.

 FIX #33874 Turn on/off ALL selected layers with "Space" button

The "_search_frame_" hidden column should only be added for layers
with geometries.
It was the first column of the virtual table, it is now the last

…le proj

folder

This is a stupid stupid situation, but because of the mess which is
QGIS application initialization we have to be very careful that nothing
creates a QgsCoordinateReferenceSystem or QgsCoordinateTransform object
between the QgsApplication construction and the call to QgsApplication::init
with the correct profile path.

The QgsApplication constructor creates the members object which contains
singleton-ish things, and this CANNOT POSSIBLY be moved out of the
constructor. And since it's apparently impossible to know the correct profile
path at time of QgsApplication construction, we are left with the only
option of ensuring that NOTHING in the QgsApplication members creates
QgsCoordinateReferenceSystem or QgsCoordinateTransform objects (because if they
do, then the proj search paths can't correctly be set to the actual
profile path -- because until QgsApplication::init is called we don't
know what the profile path is)

Long story short: QgsTaskManager constructor was connecting to the QgsProject
instance, forcing early construction of QgsProject and a QgsCoordinateReferenceSystem
object as a result. F̶i̶x̶ gross hack around this by deferring the connection until
a task is actually created, by which time we e̶x̶p̶e̶c̶t̶ hope that the call to
QgsApplication::init has occurred...

This is all l̶o̶v̶e̶l̶y̶ a pile of s***, and needs to be re-thought for QGIS 4.0

Fixes #35427

Fix #34331

…eve the

current set of parameters for other parameters when required

This is cleaner, because the panel owns all the wrappers required
to evaluate the parameter values

[RPM] add build dependencies for vector tiles

* fix 3D crash with measure line

* avoid non wanted windows opening of identify tool and measurment tool

* adds guard avoid crashing when closing settings

* spelling

option to define multiple bands parameter in modeler parameter defintion
dialog

defaultToAll option to modeler parameter definition dialog

widgets to C++

missed number type and min/max options

and map layer parameters

Allows marker symbols to be placed directly on layouts, eg.
for manually placing markers over a map item or for creation
of advanced custom legends

marker items are placed with a single click instead of click-and-drag

[infrastructure] [macos] use QGIS-Mac-Packager dependencies to setup MacOS CI build with GitHub workflows. Use CMake's define QGIS_MAC_DEPS_DIR to define folder to dependencies

+ fix layer extent when reading vector tiles from MBTiles

This reverts commit aa1c3e1.

The change breaks a test

Fixes a segfault if translation of word "Acceleration" does not match.