Re: "wxt on Mac": news

[<tim...@en...>]

> On Friday 30 March 2007 10:41, Timothée Lecomte wrote:
>> So there is one remaining thing to try, but this will involve more work
>> on
>> my part: changing the way wxt works on Unix and Mac and arrange it so
>> that
>> the main thread runs the event loop while the usual gnuplot command-line
>> loop runs in the separate thread.
>
> Won't this prevent switching to another interactive terminal type?
>
> Sounds to me that Cocoa is broken by design.

Well, X11 is more flexible, but has its own little problems ;) Note that
Windows has the same limitation (GUI loop in the main thread).
My thinking is more than gnuplot was bit designed for this kind of things.
I have put a lot of thoughts into a better design, I'm not quite there
yet, but we never know ... (it's quite close to our problem with "keep
processing terminal events even when it's not the current one" for which
we have an entry in the tracker).

> Given this design limitation,
> I suspect it would be easier/better to use the gnuplot+gnuplot_x11 model.
> Instead of running wxt as a daughter thread, spawn a separate process
> for which it is the main thread.
>
> 	Ethan

That's an option, with its own issues (locating the executable, using an
interprocess communication mechanism - pipes are not available on Windows
-, bottlenecks in this mechanism, etc.).

Timothée