Piotr Zgorecki <[EMAIL PROTECTED]> writes:
> On Sat, Apr 12, 2003 at 12:02:21PM -0400, Dan Espen wrote:
> > If you have xev installed, you might try to use it to figure out
> > whats happening.
> > 
> Ok. Here's its output:
> 
> For 'Mouse 4      A    M    Exec aumix -v+1':
> 
> KeyPress event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24424081, (83,135), root:(680,200),
>     state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
>     XLookupString gives 0 characters:  ""
> 
> LeaveNotify event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24425486, (83,135), root:(680,200),
>     mode NotifyGrab, detail NotifyAncestor, same_screen YES,
>     focus YES, state 2056
> 
> EnterNotify event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24425486, (83,135), root:(680,200),
>     mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
>     focus YES, state 2056
> 
> KeymapNotify event, serial 26, synthetic NO, window 0x0,
>     keys:  70  0   0   0   0   0   0   0   0   0   0   0   0   0   8   0   
>            0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> ButtonPress event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24425486, (83,135), root:(680,200),
>     state 0x8, button 4, same_screen YES
> 
> ButtonRelease event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24425486, (83,135), root:(680,200),
>     state 0x808, button 4, same_screen YES
> 
> KeyRelease event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 24426544, (83,135), root:(680,200),
>     state 0x8, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
>     XLookupString gives 0 characters:  ""
> 
> 
> And for 'Mouse 5      A    M    Raise':
> 
> KeyPress event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 25382743, (121,117), root:(718,182),
>     state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
>     XLookupString gives 0 characters:  ""
> 
> LeaveNotify event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 25383903, (121,117), root:(718,182),
>     mode NotifyGrab, detail NotifyAncestor, same_screen YES,
>     focus YES, state 4104
> 
> FocusOut event, serial 26, synthetic NO, window 0x2200001,
>     mode NotifyGrab, detail NotifyAncestor
> 
> FocusOut event, serial 26, synthetic NO, window 0x2200001,
>     mode NotifyUngrab, detail NotifyPointer
> 
> FocusIn event, serial 26, synthetic NO, window 0x2200001,
>     mode NotifyUngrab, detail NotifyAncestor
> 
> KeymapNotify event, serial 26, synthetic NO, window 0x0,
>     keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   8   0   
>            0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> EnterNotify event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 25383905, (121,117), root:(718,182),
>     mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
>     focus YES, state 8
> 
> KeymapNotify event, serial 26, synthetic NO, window 0x0,
>     keys:  70  0   0   0   0   0   0   0   0   0   0   0   0   0   8   0   
>            0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> KeyRelease event, serial 26, synthetic NO, window 0x2200001,
>     root 0x46, subw 0x0, time 25384651, (121,117), root:(718,182),
>     state 0x8, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
>     XLookupString gives 0 characters:  ""
> 
> 
> > Yes, I understand now, but the mystery remains.
> > 
> It surprised me too. Maybe it's my XFree? I have Debian's
> 4.2.1. Unfortunately I don't have any non-debian system with X to
> check this.

I haven't forgotten about this.

I just have no clue.

Your traces show button 4 getting passed to xev, but not button 5.

I can't reproduce it.

-- 
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]

Reply via email to