On 17 October 2013 06:08, Thomas Martitz <thomas.martitz@student.htw-berlin.de> wrote:
Am 16.10.2013 21:04, schrieb Dimitar Zhekov:


Actually, I finished most of it, what remains is mainly blocking Geany
while the new async tools execution is running.

Sync spawning is not good, because I'm using the Geany message loop for
async I/O (somewhat similar to g_main_context_add_poll), not real Win32
events and threads as GLib does.

Locking the file, as Matthew suggested, will not be sufficient: one can
still close it, reload it, and of course change the selection
(SCI docs assume close/reload are be blocked for background saving).

What remains, without going too deep, is a modal dialog. Annoying, of
course, but with the benefit that you can easily stop a bad process.


I may have missed it but why have it blocking if async spawn now works? The current build process (on Linux) doesn't block either.

I think Dimitar is talking about for tools use where the results of the command are pasted to the buffer, so the existence of the buffer and the selection should not change while the command is running.
 
Cheers
Lex


Best regards

_______________________________________________
Devel mailing list
Devel@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/devel