Jeff Epler
a86ac40e4a
The intent of this use of glBitmap is to move the raster position without drawing anything. However, it may be required to use None instead of the empty bytes object for this. I couldn't quite verify this as I don't have an affected system. The final argument is the 'bitmap' argument. The use of a NULL bitmap together with nonzero xmove/ymove parameters is explicitly documented as a valid way to move the raster position (including to offscreen positions); doing it with a zero byte bitmap is apparently unsupported in some OpenGL implementation even if the width×height of the bitmap is 0 pixels. https://docs.gl/gl3/glBitmap specifically documents that negative width and height are errors, but doesn't document that a height or width of 0 is invalid. |
||
|---|---|---|
| .. | ||
| designer | ||
| lib | ||
| plugins | ||
| widgets | ||
| __init__.py | ||
| core.py | ||
| logger.py | ||
| qt_action.py | ||
| qt_istat.py | ||
| qt_makegui.py | ||
| qt_makepins.py | ||
| qt_pstat.py | ||
| qt_tstat.py | ||
| qtvcp_handler.py | ||
| README.txt | ||
| test1.ui | ||
at the moment to use designer one must create links from (hardy), Wheezy uses slightly different location /usr/lib/qt4/designer/python/ (linuxcnc plugins) to: RIP_folder /lib/python/qtvcp_widgets/widget_plugins/ (linuxcnc plugins) for testing purposes there are two test files in RIP_folder /lib/python/qtvcp. test1.ui is for hal only widgets loadusr qtvcp test1.ui test2.ui is for testing/interacting with a running linuxcnc session. test2 requires the handler file, qtvcp_handler to be loaded. loadusr qtvcp -u qtvcp_handler test2.ui