[Bugs] #4068 sugar-toolkit-gtk3 HIGH: Hidden cursor can have an action
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Mon Nov 5 16:59:55 EST 2012
#4068: Hidden cursor can have an action
-----------------------------------+----------------------------------------
Reporter: erikos | Owner: erikos
Type: defect | Status: new
Priority: High | Milestone: 0.98
Component: sugar-toolkit-gtk3 | Version: 0.97.x
Severity: Major | Keywords:
Distribution: OLPC | Status_field: Assigned
-----------------------------------+----------------------------------------
Comment(by dsd):
There is some weird interaction with the mouse cursor and the touchscreen.
In Sugar, playing on an empty group view (I have no friends), I do the
following:
1. As preparation, use the touchpad to position the mouse cursor
somewhere on the left half of the screen
2. Briefly touch somewhere on the right side of the screen
3. Use the touchpad to move the cursor very slightly
4. Briefly touch somewhere on the left side of the screen
5. Use the touchpad to move the cursor very slightly
6. Repeat steps 2 through 5 until bored
The result is that touching the screen always moves the mouse cursor to
the location of the touch (you can't see it, but move the mouse slightly
and you'll find its new location).
Now, in GNOME:
1. Start GNOME, wait for it to load, don't touch any input devices. Note
that the mouse pointer is in the centre of the screen.
2. Touch the screen somewhere on the right hand side.
3. Use the touchpad to move the cursor very slightly
You'll notice that the mouse cursor jumps to the touch point when you
execute number 3, just like Sugar. But now keep playing:
1. Touch the screen somewhere on the left side
2. Use the touchpad to move the cursor very slightly
3. Repeat 1 and 2 until bored
Now we are seeing different behaviour. Touching the screen does *not*
affect the position of the mouse cursor like the previous tests.
But when you open a GNOME app or two and start tapping in and out of
windows, we lose that behaviour.
Having trouble getting my head around what kind of behaviour we want here,
and if it relates to this bug.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/4068#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list