Skip to the navigation links
Last modified: 11 October 2018


Bugs: windows & the display setting

Table of Contents




Turning off redraw may be slow when running remotely

Turning redraw off by calling

set_window(["display", False])

can be a very slow command especially if running remote. It may be faster to start with the window display off, or if grouping commands in atomic units, use undo buffers.


When display is turned off, the font display may have rendering problems.

This is most noticeable on axes tick labels, but can also be seen with other text.


Try changing the window display to True before calling print_window; e.g.

set_window(['display', True])

Undo-ing a window delete

Calling undo after deleting a window which had its redraw parameter set to False will re-create the window but display all its contents on screen (it does not respect the redraw state).

Trying to create large windows

Users may experience problems when trying to create large plot windows that exceed the size of the physical display. When the physical height or width is exceeded, chips may reset that value back to the default value which is 360 pixels. The exact limit depends on the display geometry but it is suggested users not try to create windows larger than 2000 x 2000 pixels.

Users can use the "scaleheight" and "scalewidth" parameters to reduce the plot window size. However, they may still experience problems if they try to export the file as full scale resolution if the export size exceeds the display dimensions.

Cannot run without DISPLAY on OS-X (Xvfb crashes)

Trying to run Chips without the DISPLAY set does not work on OSX. The default off-screen rendering utility, Xvfb, crashes on startup.