|
From: <tim...@en...> - 2006-07-27 20:20:01
|
Ethan A Merritt wrote: > On Thursday 27 July 2006 01:26 pm, Timoth=E9e Lecomte wrote: > =20 >> Ethan Merritt wrote: >> =20 >>> I suggest that wxt should work similarly. When gnuplot sees that 'ex= it' >>> command, it should set a flag for wxt to see. With the flag set, all >>> operations that require code outside the wxt driver itself should be >>> disabled. >>> =20 >>> =20 >> In the case of wxt, gnuplot is still there and the routines definitely= =20 >> available. >> On the other hand, disabling all operations that require core routines= =20 >> means disable all mouse routines. That would be sad. >> =20 > > But if you want to continue using gnuplot, why did you exit from it? > =20 I guess the idea was to use "persist" when gnuplot exits _itself_, i.e.=20 when the input is a script and gnuplot reaches the end. > As I see it, the keyword "persist" means > "Keep the last plot on the screen even after gnuplot goes away". > =20 That's how it works for the x11 terminal. But as wxt (and the windows terminal too) lives _in_ gnuplot, this=20 meaning doesn't make sense anymore, and becomes : "Don't exit until all plot windows are closed." And then, why not supporting mouse operations since we can ? > Post-4.2 we can re-examine what additional operations are reasonable to > support while in this persistent state. This is directly analogous to = the > set of mousing operations it would be possible to support in an embedde= d > SVG plot. Since gnuplot itself is no longer around at the time of > interaction with the SVG document, all information for mouse interactio= n > must be embedded with it. =20 > > For example, I'd like to rework zooming so that it does not require > re-reading data from a file. I also have a couple of plans for post-4.2 regarding mouse interaction,=20 now that I am a bit more familiar with the current behaviour. The svg stuff seems very exciting by the way. Best regards, Timoth=E9e |