and enhance perf of reading from stdin. Note that for that later mode,
I'm not sure if there are unit tests, but hopefully the OGC integration
tests should cover this?
The check for ``width * depth + 31`` not overflowing INT_MAX was done
after computing it, which would be undefined behavior if that happened.
Nowadays compilers can use "impossible situations" in smart ways, and
could very well discard the check if it is done afterwards. Be on the
safe sife and check before, as done in
https://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/image/qimage_p.h#n89
In the textured case, the diffuse parameters have no
effect. Therefore, `mDiffuseCoefficientWidget` needs to be hidden.
Closes: https://github.com/qgis/QGIS/issues/56750
This custom QLayout class allows for overlaying child widgets on top
of their parent widget.
It can be used like this:
layout = QgsOverlayWidgetLayout()
parent_widget.setLayout(layout)
layout.setContentsMargins(20,20,20,20)
layout.addWidget(QGroupBox(), Qt.Edge.LeftEdge)
layout.addWidget(QLabel('My label on top of a parent!'), Qt.Edge.TopEdge)
layout.addWidget(QGroupBox(), Qt.Edge.TopEdge)
Previously we just used the background thread to prefetch all the
attribute values in advance, and then calculated the stats on the
main thread. This had a number of downsides:
- It would block main thread while iterating over the collected
values and calculating stats
- It required storage of ALL the fetched attribute values in a
container. By just passing these values immediately to the stats
summary classes, there's optimisations in place which will avoid
storing all values wherever possible.
- There was custom logic to handle null values, when we should
be relying on the standard logic from the stats summary classes
to be consistent with other places in QGIS
Small tweaks to running in Qt 6(removed obsolete method calls
QTime().start() and QTime().elapsed(), and changed an overloaded slot
(QComboBox::activated()) to a non-overloaded one (textActivated()).
- layer name
- tile size
- feature limit for GetFeatureInfo
These were all non-functional widgets in the WCS source panel,
which were not used anywhere(!)
Similar to the existing setting for temporal filtering of 2d layout
maps, this setting allows users to set a specific elevation/z range
for a layout map item. When set, map layers with support for 2d
z range filtering (currently point clouds and raster DEMs) will
be filtered to show only content within this range.
The z range can be data-defined, allowing differing z range
for different atlas or report features.
