Starting at python 3.10, the rules for passing floats into python C extension modules like pyqt has gotten stricter.
See #951 (closes #951)
The analog indicator widgets have this issue, but they mask over it with try/except blocks to prevent the app from crashing.
This PR makes the widget render as intended by casting all variable inputs to int.
Some of these are guaranteed to always be ints, but some of them are floats. Rather than parse out which is which, I figured it was better to cover all of them.
Starting at python 3.10, the rules for passing floats into python C extension modules like pyqt has gotten stricter. See #951 (closes #951)
The analog indicator widgets have this issue, but they mask over it with try/except blocks to prevent the app from crashing. This PR makes the widget render as intended by casting all variable inputs to int. Some of these are guaranteed to always be ints, but some of them are floats. Rather than parse out which is which, I figured it was better to cover all of them.
Python 3.9 pre-PR:![indicatorpy39](https://github.com/slaclab/pydm/assets/10647860/80da08cf-0a64-4836-aa01-ba12a2789e5f)
Python 3.12 pre-PR:![indicatorpy312](https://github.com/slaclab/pydm/assets/10647860/4a7b1d58-767c-46fd-97d8-2c4b959beb8b)
Python 3.12 post-PR:![indicator312_fixed](https://github.com/slaclab/pydm/assets/10647860/b2d3f7fb-d371-49d8-8cd0-0b8a8d24e3fa)