|
From: Bastian M. <bma...@we...> - 2014-02-26 06:46:42
|
Am 26.02.2014 06:39, schrieb Daniel J Sebald: > On 02/24/2014 09:59 AM, Jérôme Lodewyck wrote: >> 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. > FWIW, Qt runs nicely on Windows. The only real issue there was to implement a way to handle all possible types of events (console, stdin, Qt pipe, Windows messages) at the same time. That has been solved in a non-portable way, but so is the code using select() on Unix-like systems. See the ChangeLog entry on 2014-02-14 and the SF patch tracker #645. Bastian |