** Changed in: unity8 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse events, puts device
** Changed in: autopilot (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse events,
** Branch linked: lp:~mzanetti/autopilot/dont-use-touchpad-for-touch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse events, puts
Thanks for this information Chris. I've ran this while watching the
debug output for unity8 and turns out the above you registers a device
with the evdev property ID_INPUT_TOUCHPAD. A touchpad is considered a
desktoppy thing too, hence switches to windowed mode too.
I have modified your example
And here's the code in AP:
/usr/lib/python3/dist-packages/autopilot/input/_uinput.py:
def _get_touch_tool():
# android uses BTN_TOOL_FINGER, whereas desktop uses BTN_TOUCH. I have
# no idea why...
if autopilot.platform.model() == 'Desktop':
touch_tool = e.BTN_TOUCH
else:
** Branch linked: lp:~canonical-platform-qa/autopilot/overlay_fix-touch-
device
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse
For now I'm changing the default setting in unity to stick to Staged
mode.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse events,
Actually the requirement should be to enable autopilot tests to choose
different input devices. For example some function method decoration to
specify which types of input devices (touchscreens, keyboards, mice..)
should be plugged for a particular test.
--
You received this bug notification
Digging into this its not 'Mouse' events triggering this (you cannot create a
Mouse instance on a device without installing all the XLib stuff).
It's the creation of a Touch device that is triggering this. You can observe
this by shelling into a device and starting python3 terminal:
from
9 matches
Mail list logo
