|
From: sfeam <sf...@us...> - 2014-11-16 01:12:10
|
On Saturday, 15 November 2014 05:02:52 PM sfeam wrote: > On Saturday, 15 November 2014 07:56:05 PM Allin Cottrell wrote: > > > Here are my results (again, with today's CVS): > > The behaviour you report is different in detail from what I see here. > > > > 1) I do: gnuplot -persist <plotfile> > > > > The dialog opened by the wxt wrench icon shows the "persist" box > > checked; it always takes a long time for the Save dialog to appear. > > I don't see any delay at all for this test case Oops. Sorry, I misunderstood. Yes I do see the delay for this case if the <plotfile> exits rather than issuing "pause mouse" or something of the sort. Ethan > > > > 2) I do: gnuplot (interactive) ; then 'load' plotfile > > > > a) If I click the wxt wrench icon, the dialog shows the "persist" > > box checked. If I click the Save icon while the calling gnuplot > > instance is still active, it always works instantly. > > yes > > > (b) If I type 'quit' in the calling gnuplot instance, then try the > > Save icon in the wxt window, sometimes the Save dialog still comes > > up instantly and sometimes it takes ages. I haven't yet determined > > if there's any reliable predictor for the variant behaviors. > > this is the case in which I see a delay. > 'quit', or simply running gnuplot -persist file.gp, > causes the main process to exit, leaving a subprocess > to manage the persistent plot window. This is the state > from whihc the toolbar button is slow to respond. > > Ethan > > > > Allin Cottrell > |