On Tue, Jun 29, 2004 at 12:53:27PM -0500, fvwm-bug wrote: > FVWM Bug Tracking notification > > new message incoming/1335 > > From: [EMAIL PROTECTED] > Subject: FakeClick generates EnterNotify event > > Full_Name: Piotr Zielinski > Version: 2.5.10 > CVS_Date: > OS: Red Hat Linux 9 > X_Server: 4.3.0 > Submission from: (NULL) (128.232.8.138) > > > I use FakeClick to intercept clicks in some windows, and pass the click to > the others, for example > > AddToFunc HandleClick > + I PointerWindow (FvwmPager) DoSomethingSpecial > + I PointerWindow (!FvwmPager) FakeClick depth 0 press 1 > > This sometimes doesn't work. For example, in xdvi should react to such a > click by displaying a window containing a magnified version of some part of > the document as long as the button it pressed. It does not.
Please carefully read the description of the FakeClick command in the man page. A binding like yours can not work reliably with all applications. Windows need to be clicked at various "depth" values, and it's impossible to know without trying. In case of xdvi the problem is that is does not react to the button press but to the button release. You can try + I PointerWindow (!FvwmPager) FakeClick depth 0 press 1 release 1 or shorter + I PointerWindow (!FvwmPager) FakeClick d 0 p 1 r 1 > Using xev I > discovered that FakeClick produces an additional EnterNotify event just > after the button has been pressed. > > Is this a bug? No. EnterNotify and LeaveNotify events are generated by the X server automatically when a button is pressed or released. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED]
pgpearzr47WrE.pgp
Description: PGP signature
