- fixed handling of foreground colors in AxisItem
- fixed rare crash caused in AxisItem
- fixed improper propagation of key events from SpinBox
- many others
- avoid sending keyboard interrupt signals to child processes
- parallelizer keeps better track of processes that die unexpectedly
- added ability to specify a different executable when starting new processes
- Fixed some floating-point precision issues. (Added a workaround for QTransform.inverted() bug)
- No longer putting asUnicode inside __builtin__ since this causes problems in some rare circumstances
(pyshell, lazy import recipe)
- Minor docstring updates
- Added pyqtgraph.systemInfo() for bug reporting
- GraphicsLayout does a better job of avoiding occupied cells when using automatic placement
- Fixed sizing issues with LabelItem
- Updated GraphicsLayout example
- ForkedProcess is much more careful with inherited state -- closes file handles, removes atexit and excepthook callbacks
- Remote processes copy sys.path from parent
- Parallelizer has ProgressDialog support
- Many docstring updates
- Added some test code for remote GraphicsView rendering
- allows starting new processes and controlling them remotely from the parent process
- remote processes can run their own GUI, Qt signals can be connected between processes
(in general this is not possible with the built-in multiprocessing module due to
the use of fork() ).
- Control works by a system of proxy-objects such that controlling a remote process
looks almost exactly like working with local objects.
- Uses sockets to communicate between processes (so in theory could be made to
work over a network), but also includes a mode that uses fork() to allow fast
parallelization.
- Wicked-easy inline parallelization by adding only one line of code to break up work between
processes (requires fork; sorry windows users)
- GUI interactive python prompt, useful in a variety of situations where
python -i or ipython don't work very well.
- Command history (requires a little help finding storage for this)
- Exception catching, allowing the user to inspect local variables
at any level within a stack trace (currently, this is done _without_
blocking the application)
