On Fri, 17 Dec 2010 18:59:29 +0000 (GMT), Michael Drake wrote:
> In article
> <[email protected]>,
> Chris Young <[email protected]> wrote:
> > On Fri, 17 Dec 2010 12:39:03 +0000 (GMT), Michael Drake wrote:
>
> > There might be a problem somewhere though, see my other message.
>
> Try calling browser_mouse_state_dump() at the top of the
> tree_mouse_action() function in desktop/tree.c. If you start an edit,
> move the pointer out the edit area and find out what's logged, it might
> shed some light.
Loads of blanks, except:
(19.834372) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.836845) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.852678) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.869620) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.876669) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.883726) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.903924) desktop/mouse.c browser_mouse_state_dump 46: mouse state:
M2
(19.911971) content/llcache.c llcache_clean 1613: Attempting cache clean
(19.918947) content/llcache.c llcache_clean 1683: Size: 155979
(20.200233) desktop/mouse.c browser_mouse_state_dump 46: mouse state: P1
M2
(20.270057) desktop/mouse.c browser_mouse_state_dump 46: mouse state: P1
M2
(20.278605) desktop/mouse.c browser_mouse_state_dump 46: mouse state: C1
M2
(21.61202) desktop/mouse.c browser_mouse_state_dump 46: 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?
Chris
