On 10 May 2001 12:35:27 +0200, Dominik Vogt wrote: > > On Wed, May 09, 2001 at 11:12:26PM +0000, Mikhael Goikhman wrote: > > On 09 May 2001 01:48:44 +0200, Dominik Vogt wrote: > > > > > > On Tue, May 08, 2001 at 09:58:24PM +0000, Mikhael Goikhman wrote: > > > > I don't know when this started. > > > > > > > > AddToFunc TestFunction I Wait "unexisting window" > > > > TestFunction > > > > > > > > Now, click or drag using the mouse anywhere. Woops, mouse is mostly > > > > locked. The keyboard works well (did I say something similar before?), > > > > so you may quit this mode by pressing Ctrl-Alt-Escape. > > > > > > That's not really new. This was always the case if the function > > > used anything else but 'I'. I don't know what to do about that. > > > The pointer must be grabbed during function execution for the > > > reasons I explained in the thread with Paul's deiconify problem. > > > > I think I see this thread and I can't find where is explained why the > > cursor grabbing is needed. > > >From the ChangeLog: > > 2001-03-22 Dominik Vogt <[EMAIL PROTECTED]> > > * fvwm/functions.c (execute_complex_function): > fixed button presses being passed to other applications with functions > that only have immediate actions > > > This locked cursor behaviour is not good. Wait is mostly used in "I" > > functions. It is used in many places, including fvwm-themes, FVWM FAQ. > > No, it's not good at all.
So, what do we do about this? A possible solution is to ungrab cursor before some commands (Wait) and then grab again. If there is no solution, I think we should disable this commit, because it is problematic. I run a version with this commit disabled during a week now, so I may do it. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
