|
From: Allin C. <cot...@wf...> - 2014-11-16 14:28:50
|
On Sun, 16 Nov 2014, Daniel J Sebald wrote: > Generally, gnuplot is not using wxWidgets event loop (because otherwise it > would be unable to do anything). But then, when gnuplot exits with persist, > it passes event loop processing off to wxWidgets using wxTheApp->OnRun(). > > However, that means that even though the wxWidgets objects function properly > (because events are handled by OnRun()) gnuplot can no longer manage events > or in fact do anything. I just confirmed that is the case. The WXT plot > window left behind by persist is basically frozen. Try right mouse click, or > scaling the window and the plot is fragmented. [...] I don't find that to be the case at all. The wxt window left open by "gnuplot -persist plotfile" works fine, in general: it resizes correctly, responds to right-mouse as expected, and all the menu buttons work apart from the delay in the case of Save. The same goes for the case where gnuplot is started interactively, a wxt plot is displayed, then I do "quit" at the gnuplot CLI: the wxt window works fine apart from Save. Re. the file dialog I suspect there's some sort of required gvfs/gio initialization that is not being inherited (fully) by the child on fork(). Allin Cottrell |