On Thu, Jul 30, 2009 at 4:24 AM, Jason Foutz<jfo...@gmail.com> wrote: > > I'm not familiar enough with yi to know where to put the split, but > yeah, approach sounds exactly right. > Somewhere, you'll have some code that looks just about like this. > [...]
Agreed, this might improve the situation. However, an important part is missing in that code: how is the channel going to be filled? I guess whenever an event comes from gtk. Therefore the "ui" thread must also fill in an event channel somewhere. Now, this structure existed a couple of years ago in Yi, but gtk2hs did not support threading properly, and therefore channels have been replaced by synchronous function calls. This was implemented in a patch by Krasimir Angelov around April last year (I think). There is still trace of this structure in the code, so I don't think it would be difficult to revert. However, I don't know if threading in gtk2hs has improved much since then. Cheers, JP. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
