On 24/01/11 03:51, Albrecht Schlosser wrote:
> On 23.01.2011 17:08, Greg Ercolano wrote:
>> Ben Stott wrote:
>>> DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK 
>>> BELOW.
>>>
>>> [STR New]
>>>
>>> Link:http://www.fltk.org/str.php?L2493
>>> Version: 2.0-feature
>>>
>>      Cool, someone's fixing 2.0 STR's!
> Yeah, welcome to the team, Ben !
>
>
Thanks guys! :)

> ... and while we're at it :-) I read the discussions about this
> STR with interest, and I noticed that you had looked at FLTK 1.3
> as well in one of your statements:
>
> "upon digging, I noticed that FLTK1.x suffers the same fate with its use
> of fl_xevent->xbutton.xstate (which only proves that this "bug" is
> consistent between FLTK version), however the default RELEASE event
> seems to handle things in a different way, which seems to sidestep this
> bug and provide the desired result.
> I can provide a patch for both versions"
>
> Do you have a concrete suggestion for FLTK 1.3? Should we simply
> discard these two special bits? I could look into it myself, but
> since you seem to know better what's going on...
I really only took a brief look, but FLTK caters for 7 events whereas X, 
by default, only caters for 5. Thus, when the fl_xevent->xbutton.xstate 
value is shifted, FLTK ends up keeping 2 bits of X garbage, and it was 
these two bits that were causing the problems in 2.0.
1.3 seems to manage it's FL_PUSH/FL_RELEASE events slightly differently 
to 2.0, which subverts this whole problem - 2.0 checks for ANY_BUTTON 
being pressed (and since X only returns 5 buttons by default, whereas 
ANY_BUTTON is an 8-button mask, this causes the reported bug).
So at this stage, there's no real concrete suggestion. The state mask 
works, but I don't know how well it works on a mouse with 7 or 8 buttons 
- I'm testing this currently, but in order to do that I also need to add 
in horizontal scroll support. I'll have more time to look at this 
tonight.....

Ben


_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to