Re: [Texmacs-dev] Two fixes for delayed execution

[Joris van der Hoeven]

On Sat, Oct 17, 2009 at 12:15:08AM +0200, Gubinelli Massimiliano wrote:
> I agree that something like this should work. What about the following  
> more uniform scheme:
> each Qt event handler performs some basic computations (which do not  
> require involvement of TeXmacs objects)
> enough to determine an appopriate function call into TeXmacs which is  
> then boxed as abstract command  and inserted in the
> delayed messages  queue. This would allow to return as fast as  
> possible to the event loop. Inside check_events should then be safe to  
> call processEvents which could result in filling up the delayed- 
> messages queue by some input commands (keypresses or mouse movements).  
> If this is the case we can set some flags so that check_events can  
> interrupt the drawing process and return to the main event loop. At  
> this point the delayed messages can be processed. This would have the  
> added bonus of giving us the control of the events already  
> preprocessed so that, for example, we can skip some mouse move events  
> if they are too many, or process all the key events, etc...
> I still have some doubts about the handling of socket events.

If this would not be t much a hassle for you to implement,
then this seems like an excellent idea. Indeed, at certain times
it can be interesting to preprocess the input events.

Best wishes, --Joris