In article
<[email protected]>,
Chris Young <[email protected]> wrote:
> Loads of blanks, except:
> mouse state: M2
> mouse state: M2
> mouse state: M2
> mouse state: M2
> mouse state: M2
> mouse state: M2
> mouse state: M2
> mouse state: P1 M2
> mouse state: P1 M2
> mouse state: C1 M2
> mouse state:
> ...which suggests I've clicked the mouse whilst holding modifier 2
> (which is exactly what I have done).
> There are two instances of P1 which I don't think is right, but
> neither would I expect a spurious press at that stage to cause this
> problem.
> Any ideas?
You should only pass modifiers when there is also other actual mouse
action. So you should never get M2 (or M1 or M3) on its own.
Also, I'm concerned about "Loads of blanks". You shouldn't get any
blanks. If the mouse isn't clicking or dragging the treeview shouldn't be
informed about it.
And yeah, the two presses is wrong. You should get just:
mouse state: P1 M2
mouse state: C1 M2
--
Michael Drake (tlsa) http://www.netsurf-browser.org/
