|
From: Bastian M. <bma...@we...> - 2014-10-25 18:05:48
|
Am 25.10.2014 um 19:46 schrieb Daniel J Sebald: > On 10/25/2014 03:40 AM, Daniel J Sebald wrote: > >> I removed the interlock test and it creates quite a mess with invalid >> events, seg faults in bad library calls, to scratch the surface. >> >> Investigating a bit, I think the problem lies in the fact wxt terminal >> is not in its own process. > > It's too much work to do this in an afternoon or so. Having looked at > the code, though, I'd say some things get simplified when WXT is run in > its own process as an outboard plotter. All these sorts of conditions > > #if defined(WXT_MONOTHREADED) || defined(_Windows) > > go away. > > Dan Btw. Timothée had been working on this years ago, see patch #380 https://sourceforge.net/p/gnuplot/patches/380 Also, the qt and wxt terminals run nicely in the same session on Windows. It just took some effort to make qt->waitforinput() work. Since waitforinput() is a terminal routine it typically only handles events from the library the current terminal uses. If we want to use multiple libraries in the same process, we need to replace/extend that mechanism. From my experience with the (outboard) qt terminal, I sincerely doubt that moving the wxt terminal to its own process will significantly simplify the source. Bastian |