Hey Daniel,
It seems if my rotation is 0 or 180, touch works correctly. Maybe it’s related
to whether my button array fits on the screen entirely.
If it’s 90 or 270 (or if the image is partially off-screen), the touch
coordinates are off.
Does anyone have any idea where I should look to align
Thanks Daniel,
My local test is just a timer that rotates every 5 seconds. I have a python
keyboard running that rotates, but I have remnants of the original keyboard.
Almost like I have a stale buffer. The extra keyboard images don’t respond
either.
Is there some clear I need to be calling b
Thanks Daniel,
Excellent information.
I had a thought on the patch, what if the iio part were something that ‘could
be implemented’ by end developers (as the hardware dictated), but a way to
rotate
would exist. Maybe an ipc socket could be a generic means to implement a
rotation. That way,
Hi Guillermo,
On Fri, 6 Aug 2021 at 10:44, Guillermo Rodriguez Garcia
wrote:
> El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
> escribió:
>> kiosk-shell is something we have in newer versions of Weston which
>> sounds like it would work well for your usecases - it's designed to
>> just run a si
Hi Daniel,
El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
escribió:
> kiosk-shell is something we have in newer versions of Weston which
> sounds like it would work well for your usecases - it's designed to
> just run a single application fullscreen. You might want to check out
> what we have in
Hi David,
On Thu, 5 Aug 2021 at 22:17, David Deyo wrote:
> > Sounds like you're missing wl_display_flush() in your client code, so the
> > requests don't make it to the socket buffer until they're forced to because
> > it's filled up.
>
> That did it. You guys are awesome. I don’t suppose the
