On Fri, Jan 16, 2004 at 10:50:08AM +0100, Uwe Pross wrote:
> Hi there,
>
> A couple of weeks ago I reported an nerving beep when
> opening FvwmWindowList or menus of some programs. In the
> last days I used FrameMaker which shows this behaviour quite
> often when a submenu is opened and closed. I added some
> debug statement to 2.5.7 to see where the beep comes from.
> It says that the beep comes from functions.c [987]:
>
> /* we have to grab buttons before executing immediate actions because
> * these actions can move the window away from the pointer so that a
> * button release would go to the application below. */
> if (!GrabEm(CRS_NONE, GRAB_NORMAL))
> {
> func->use_depth--;
> fprintf(stderr,"*** FVWM Bell: %s line %d ***\n", __FILE__,
> __LINE__);
> cf_cleanup(&depth, arguments);
> return;
> }
>
> I have no idea what this code does. The beep in conjuntion
> with FvwmWindowList comes from the same source.
The code grabs the pointer before executing any complex function.
As it fails, another application must have already grabbed the
pointer. Is it essential to grab the pointer before starting the
menu as it may otherwise not get the button release event which is
important for menu operation.
Ciao
Dominik ^_^ ^_^
--
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]
