Op 1/27/13 11:34 PM, Miro Kropáček schreef:
Hi, I know there's a lot of GEM wizards out there, so I'd like to ask this slightly off topic question. How is programmer supposed to fight with heavy operations like loading and analyzing hundreds of files? From Qt and .net I'm used to the UI thread, events, signals but what about the poor Atari world? Is there a way how to not freeze all dialogs? I mean except the obvious things like calling refresh from the other loop after each iteration or calling each iteration from the UI mainloop.
Perhaps someone could port the MAgiC MT_.... (multitasking) AES bindings to XaAES? But already With XaAES you should be able to run int threads for each conversation in your GEM program. You must know in which thread your conversation runs, and issue appl_init/AES calls/app;_exit calls for each thread. Well, this is all theory and I do not know of antbody having tried this idee.Nor do I know whether XaAES is hread aware. However, it could be a nice idee for someone suffering of empty hands or head. :-) -- Groeten; Regards. Henk Robbers. http://members.chello.nl/h.robbers Interactive disassembler: Digger; http://digger.atari.org A Home Cooked C compiler: AHCC; http://ahcc.atari.org