On Tuesday 15 October 2002 12:31 pm, Andre Poenitz wrote:
> On Tue, Oct 15, 2002 at 12:26:52PM +0100, Angus Leeming wrote:
> > > No. This is 0 in any case. For further processing it would
> > > be nice if the button is know, though.
> >
> > So you're saying that we think we're passing the button id,
> > but in fact we're not because ev->xbutton.button is 0
> > always? Sounds like a bug to me (so the 1.3 release
> > coordinator should accept a bug fix ;-)
>
> At least that's what I get when I add lyxerr<< lines there.
>
> > Perhaps John knows as he played quite hard with all this.
>
> John, ar eyou listening?
>
> Andre'
can you extract the info from ev->xbutton.state?
man XButtonEvent:
The state member is set to indicate the logical state of the pointer
buttons and modifier keys just prior to the event, which is the bitwise
inclusive OR of one or more of the button or modifier key masks: But-
ton1Mask, Button2Mask, Button3Mask, Button4Mask, Button5Mask, Shift-
Mask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask,
and Mod5Mask.
Angus
