You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
setMaximumScale() and setMinimumScale(), maximumScale() and
minimumScale() had the opposite meaning to other min/max scales
in the API, and were the opposite to how these settings were
exposed in the GUI. This lead to very confusing API!!
Their definitions have now been swapped. setMaximumScale
now sets the maximum (i.e. largest scale, or most zoomed in)
at which the layer will appear, and setMinimumScale now sets
the minimum (i.e. smallest scale, or most zoomed out) at
which the layer will appear. The same is true for the
maximumScale and minimumScale getters.
Copy file name to clipboardExpand all lines: doc/api_break.dox
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1515,6 +1515,9 @@ screenUpdateRequested() were removed. These members have had no effect for a num
1515
1515
- readXml() and writeXml() expect QgsReadWriteContext reference as the last argument
1516
1516
- the invalidTransformInput() slot was removed - calling this slot had no effect
1517
1517
- metadata() was renamed to htmlMetadata()
1518
+
- setMaximumScale() and setMinimumScale(), maximumScale() and minimumScale() had the opposite meaning to other min/max scales in the API, and their definitions have now been swapped. setMaximumScale
1519
+
now sets the maximum (i.e. largest scale, or most zoomed in) at which the layer will appear, and setMinimumScale now sets the minimum (i.e. smallest scale,
1520
+
or most zoomed out) at which the layer will appear. The same is true for the maximumScale and minimumScale getters.
0 commit comments