Pavel Sanda wrote:
> Peter Kuemmel wrote:
>>>> I've enabled processing user input, see patch.
>>>> If it breaks anything or someone really dislikes it we could disable it
>>> again.
>>>
>>> whats the difference from users pov?
>> The GUI should not be blocked any more while processing a huge document.
>
> would it be possible to selectively switch it off for certain usage?
> i just get problem in the following scenario:
>
> triggering svn update. i dont wait until update happens and start typing.
> because
> this happens in the critical time after check for dirty buffer was done and
> update
> has not happened yet, lyx runs into clash, and lyx runs into emergency cycle.
>
> i would need that nobody touches anything while doing svn stuff.
>
> pavel
>
I've commited attached patch.
Then you could disable event processing for the svn call.
Peter
Index: src/support/Systemcall.cpp
===================================================================
--- src/support/Systemcall.cpp (Revision 32329)
+++ src/support/Systemcall.cpp (Arbeitskopie)
@@ -99,13 +99,12 @@
-int Systemcall::startscript(Starttype how, string const & what)
+int Systemcall::startscript(Starttype how, string const & what, bool
process_events)
{
string outfile;
QString cmd = toqstr(parsecmd(what, outfile));
SystemcallPrivate d(outfile);
- bool process_events = true;
d.startProcess(cmd);
if (!d.waitWhile(SystemcallPrivate::Starting, process_events, 3000)) {
Index: src/support/Systemcall.h
===================================================================
--- src/support/Systemcall.h (Revision 32328)
+++ src/support/Systemcall.h (Arbeitskopie)
@@ -42,7 +42,7 @@
* The string "what" contains a commandline with arguments separated
* by spaces.
*/
- int startscript(Starttype how, std::string const & what);
+ int startscript(Starttype how, std::string const & what, bool
process_events = true);
};
} // namespace support
