Dominik Vogt <[EMAIL PROTECTED]> writes: > On Thu, Jul 31, 2003 at 03:47:56PM +0200, Olivier Chapuis wrote: > > On Thu, Jul 31, 2003 at 11:51:59AM +0200, Dominik Vogt wrote: > > > Somethimes I feel like talking to a wall. See my previous mails. > > > > I think that you do not understand me. I see bugs that I can reproduce > > easily and I want to found a solution. I really care that fvwm can > > work well with certain applications (e.g., Mozilla and gkrellm). And > > what about all your work on autohide with the Schedule command and > > FvwmEvent (via WindowShade)? > > I'm talking only about not grabbing the pointer in complex > functions. Argue as much as you want, it does not work because it > can not work reliably under X, for example because of the way > EnterNotify and LeaveNotify events work. If you don't like it, > all you can do is to delay function execution until the pointer > can be grabbed (i.e. loop forever in certain places). But - this > may generate a deadlock with applications that grab the pointer > and then expect that the window manager processes requests.
Please don't take this the wrong way. Not all of us have your deep understanding of fvwm. If the goal is to run some functions without grabbing, why not make it an option? Like: FunctionNoGrab FUNCNAME or Grab and UnGrab comands: DestroyFunc ScreenDump AddToFunc ScreenDump + I UnGrab + I Exec xwd + ... -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
