Peter Kümmel wrote: > The splash screen will only appear when there is a ShowProgress variable > declared > before the call. But we could drop it when nobody likes it. See the diff of > Buffer.
havent understood before that splash should appear only after 2s delay, now its behaviour make more sense to me (though for eg vcs handling we would need exactly the opposite - immediate window and 2s wait to show the result... this can be parametrized i guess ;) but still don't understand the purpose. do i understand correctly that the main point of the whole switching to qprocess was that we allow background image/latex processing? > > however there are more problematic things - i wonder about all those > > waitWhile(...). > > for example this following line if > > (!d.waitWhile(SystemcallPrivate::Running, 180000)) /3000 > > means than any typeseting or external job wont work correctly if it does > > not finish in this > > limited time? or start wihin 3s? do i understand correctly that this is > > just ugly workaround > > for the non-working qt signals? > > It's not a workaround, the waitWhile functions work correctly, and the > timeout is arbitrary, so > when you think it times is too short we could increase them, or disable any > timeout when we are > sure > that the process will return. i think we should disable it by default - don't like that we will kill process which was not quick to start in 3s or kill it automatically when it took longer time to typeset/process something. apart from this i just tested QProcess branch for more usecases and it seems not to break anything. pavel
