|
From: Daniel J S. <dan...@ie...> - 2014-02-27 07:20:56
|
On 02/27/2014 12:46 AM, Jérôme Lodewyck wrote: > Le mardi 25 février 2014 23:39:38 Daniel J Sebald a écrit : >>> So could you point out a specific past or present problem in the Qt >>> terminal that is due to the fact that no event loop is running in the >>> inboard driver ? >> >> The answer is "no". But the follow up to that is I really didn't search >> for that. I'm trying to solve the problem of the Qt terminal apparently >> not working on Mac OSX or Windows the way it should in combination with >> the fact that I don't have Mac OSX or Windows. So I'm striving for an >> event loop in hopes that makes the setup work better on all platforms. I >> can't answer your question...that is, without looking into greater >> detail of the Qt source code. > > Maybe I am wrong, but I think that adding an event loop will not make things > work better. All the difficulties we had to make the Qt terminal work on all > platforms are related to correctly setting the size of the plot window I just sent a post identifying where the problem is with sizing, but it will take a little more to fix properly. > and > correctly integrating the initialization of the QLocalSocket into the workflow > of the main gnuplot program; which are problems that you will also face with > an event loop. > If you are motivated to pursue your idea, we will be able to balance whether > things are less quirky or not with an event loop, but as Ethan said, things > are already working almost correctly. The event loop is on hold. Let's clean up QProcess, QLocalSocket workflow first. Dan |