touch-packages team mailing list archive

[Michael Zanetti <michael.zanetti@xxxxxxxxxxxxx>]

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 to this (dropping the BTN_TOOL_FINGER):

mydev = UInput(events={e.EV_ABS: [(e.ABS_X, (0, 0, 0, 0)), (e.ABS_Y, (0,
0, 0, 0))]}, name='autopilot-finger', version=0x2,
devnode='/dev/uinput')

and it does not register the Touchpad any more, hence not switching to
Windowed mode. Changing the line to this:

mydev = UInput(events={e.EV_ABS: [(e.ABS_X, (0, 0, 0, 0)), (e.ABS_Y, (0,
0, 0, 0))], e.EV_KEY: [e.BTN_TOUCH]}, name='autopilot-finger',
version=0x2, devnode='/dev/uinput')

Makes it correctly register as a ID_INPUT_TOUCHSCREEN and does not make
unity8 go into windowed mode.

So seems the proper fix is to use , instead of BTN_TOUCH instead of
BTN_TOOL_FINGER in autopilot's 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 events, puts device in windowed mode

Status in autopilot package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  AP tests emulating mouse to run, which puts the device into windowed mode.
  mouse presence is used to toggle the windowed mode on mobile devices.

  ----orig bug ----
  The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor.

  See also a bunch of dubious errors below.

  Tests running...
  terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >'
  what(): Failed to send message to server: Broken pipe
  Failed to connect to server. Error was :Failed to connect to server socket: Connection refused

  (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598/+subscriptions