Currently and rendering performed in xor mode is not recorded to the
buffer. I can understand why this would be the case as xor mode is
often used for rendering temporary lines then erasing them. However,
because wxPLViewer relies on the buffer for all its rendering this
means that it cannot
On Tue, May 11, 2010 at 11:55:29PM -0500, Maurice LeBrun wrote:
I agree, xor mode sucks big time (due to the line occasionally becoming
invisible).
On a recent project, I implemented a plot overlay capability for drawing a
ruler between two interactively selected points, with coordinates
On Wednesday, May 12, 2010 at 20:18:40 (+0100) Andrew Ross writes:
On Tue, May 11, 2010 at 11:55:29PM -0500, Maurice LeBrun wrote:
I agree, xor mode sucks big time (due to the line occasionally becoming
invisible).
On a recent project, I implemented a plot overlay capability for
I've been trying to tidy up some of the inconsistencies between different
interactive drivers on plplot. The xwin, tk, qtwidget and xcairo drivers
now all more or less have consistent handling of plGetCursor as far as is
possible.
The big outstanding issue in terms of the interactive examples
On Tuesday, May 11, 2010 at 15:34:23 (+0100) Andrew Ross writes:
I've been trying to tidy up some of the inconsistencies between different
interactive drivers on plplot. The xwin, tk, qtwidget and xcairo drivers
now all more or less have consistent handling of plGetCursor as far as is