Used DC.DrawXXX functions expect integer coordinates, but this module freely mixes both float and integer values. A quick fix is to add explicit type casting in all DC.DrawXXX calls.
In the long run, either calling modules should control numeric types or DC.DrawXXX methods should handle float type as well.
I cannot tell whether the original code worked before, but this explicit typecasting is necessary now.
The issue occurs, for example if attempting to execute "PieChart.py" or "ScaledBitmap2Demo.py" in "samples\floatcanvas". Without typecasting, type errors are thrown, such as "TypeError: Image.Scale(): argument 1 has unexpected type 'numpy.float64'".
Apparently, this problem might be due to recent updates in Python and NumPy.
Fixes#2199.
The problem is that the default colour is currently wx.BLACK which will basically be invisible if the user has a dark theme. Use ``wx.NullColour`` instead so that it can just use the default text colour for the user's theme.
Note that this does not fix the second part of issue #2199 (the colours still don't change if the control is disabled) but I feel this should be a separate issue now.
PyMuPDF 1.18 renamed all of its camelCase fields and methods to use
snake_case instead, and a later version (probably 1.19) removed the
deprecated aliases. This patch attempts to use the newer name first
(since most people will probably be using a newer version of PyMuPDF)
and falls back to the older name if that fails.
In Python 3.10, a change[1] was implemented where extension functions
that take integer arguments will no longer silently accept non-integer
arguments (e.g., floats) that can only be converted to integers with a
loss of precision. This PR fixes most of these issues in the pure-Python
classes and demos by explicitly converting the parameters to int before
passing them to wxWidgets. There is loss of precision, but this was
happening before (automatically) anyway as most wxWidgets DeviceContext
functions operate using integers.
Additionally, the PR fixes a few sizing issues, mostly with SpinCtrls being
too small on GTK3.
This is an example of the relevant exception:
Traceback (most recent call last):
File "/usr/lib64/python3.10/site-packages/wx/lib/agw/pygauge.py", line 355, in OnPaint
r.width = w
TypeError: 'float' object cannot be interpreted as an integer
Fixes#2038.
[1] https://bugs.python.org/issue37999
