_CALIBRATION_MATRIX}="1
> 0 0 0 -1 1080"
>
> It should swap the y coordinate axis.
>
> regards
> Andreas
>
>
> On Thu, Feb 9, 2017 at 7:38 PM, Darren Landoll
> wrote:
>
>> I am testing the mir-kiosk snap on an amd64 kiosk/touchscreen PC. It has
>
I am testing the mir-kiosk snap on an amd64 kiosk/touchscreen PC. It has
Elo Touch based hardware and at least one of the axes appears to be swapped.
Is it currently possible to either statically or dynamically calibrate
touchscreen input for the mir-kiosk snap?
--
Mir-devel mailing list
Mir-deve
After building a custom libqpa-ubuntumirclient.so with debug, I get
the following output but don't see any additional Qt debug output when
touching the screen or pressing keyboard keys...
(amd64)ubuntu@localhost:/apps/qmldemo.sideload/current/usr/lib/x86_64-linux-gnu$
qmldemo.qmldemo
Loading modu
I set MIR_CLIENT_INPUT_RECEIVER_REPORT=log when running the qmldemo
example and observed the following...
1) After startup I tried pressing keys on the keyboard, no debug
output was shown.
2) Touches on the screen show output like the following, but are not
recognized by the application
[1447986
>
> Yes, I'm testing with the mir_demo_server snap from the store (snap1.1
> mvp-demo version). I am using a QML based application that implements
> it's own main() and loads QML files as resources.
>
> I have not tested with a QML file loaded by qmlscene in a snap though.
>
I have now tested with
>
> Hi Darren,
> the ubuntumirclient QPA has had working touch and keyboard input well
> before 15.04. Mouse events however were only more recently wired up. How
> exactly are you testing? mir_demo_server with a qml file?
> -G
>
Yes, I'm testing with the mir_demo_server snap from the store (snap1.
What is the current status of keyboard and touch input for the Mir
server and Qt QPA ubuntumirclient plug-in on Snappy 15.04?
I can enable touch spots on the Mir server and verify that touches are
detected, but my Qt/QML application doesn't appear to be notified.
Keyboard input is also not workin
On Fri, Oct 16, 2015 at 7:21 AM, Darren Landoll
wrote:
>>
>> Is this the classic problem caused by removing the runtime dependencies from
>> the Mir packaging and requiring them to be
>> pre-seeded in the system images?
>>
>> Darren, if you add the mir-grap
>
> Is this the classic problem caused by removing the runtime dependencies
> from the Mir packaging and requiring them to be
> pre-seeded in the system images?
>
> Darren, if you add the mir-graphics-drivers-desktop package (eg. to your
> oem snap) does it work?
>
It doesn't look like there is a
On Mon, Oct 12, 2015 at 6:00 PM, Kevin Gunn
wrote:
> Hey Darren - it just dawned on me, what's your host development machine on
> ? 15.04 or 15.10 ? There is a c++ abi break between 15.04 and 15.10, so you
> wouldn't be able to use mir or qt components built on 15.10 on these 15.04
> core images.
I posted this message on a different list, but after tracking down the
exception in the Mir code, it may apply more here.
I am building the amd64 oem and mir snaps and then running
ubuntu-device-flash to create either a stable or edge based image for 15.04
(in developer mode).
For initial testing
11 matches
Mail list logo
