<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hey Daniel, <o:p> </o:p> 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. <o:p> </o:p> If it’s 90 or 270 (or if the image is partially off-screen), the touch coordinates are off. <o:p> </o:p> Does anyone have any idea where I should look to align the touch with the button array, if the button widget is partially off-screen? <o:p> </o:p> -dwd <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> David Deyo<o:p></o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:.15in;border-collapse:collapse"> <tbody> <tr> <td width="150" valign="top" style="width:112.5pt;padding:0in 5.4pt 0in 5.4pt"> <img width="170" height="82" style="width:1.7708in;height:.8541in" id="Picture_x0020_3" src="cid:image003.png@01D78AE0.D0AFD290"><o:p></o:p> </td> <td width="474" valign="top" style="width:355.5pt;padding:0in 5.4pt 0in 5.4pt"> <o:p></o:p> Firmware Engineer <o:p></o:p> TPI- Tire Profiles<o:p></o:p> O: 214-396-3063<o:p></o:p> E: <a href="mailto:ddeyo@tireprofiles.com">ddeyo@tireprofiles.com</a> | W: <a href="http://www.tireprofiles.com/" target="_blank">www.tireprofiles.com</a><o:p></o:p> A: 3010 Story Rd W, Irving, TX 75038<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> <div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: <a href="mailto:daniel@fooishbar.org">Daniel Stone</a> Sent: Friday, August 6, 2021 3:14 AM To: <a href="mailto:ddeyo@tireprofiles.com">David Deyo</a> Cc: <a href="mailto:linkmauve@linkmauve.fr">Emmanuel Gil Peyrot</a>; <a href="mailto:wayland-devel@lists.freedesktop.org"> wayland-devel@lists.freedesktop.org</a> Subject: Re: FW: xrandr and xwayland </div> <o:p> </o:p> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi David, On Thu, 5 Aug 2021 at 22:17, David Deyo <ddeyo@tireprofiles.com> 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 there’s a Weston doc somewhere that would have told me that, had I looked. It's a little bit buried, but this is the best explanation of how to integrate Wayland into an event loop, as you would with a toolkit: <a href="https://wayland.freedesktop.org/docs/html/apb.html#Client-classwl__display_1a40039c1169b153269a3dc0796a54ddb0"> https://wayland.freedesktop.org/docs/html/apb.html#Client-classwl__display_1a40039c1169b153269a3dc0796a54ddb0</a> If you scroll up to the main wl_display section, it explains how event queues are used as well. Broadly speaking, the advice is to: - when active, process your events and send any requests - immediately before you go into a passive state (waiting for events, sleeping, etc), flush the display so your requests get delivered - run the prepare_read_queue() / dispatch_queue_pending() loop immediately before sleeping, in order to make sure you get all events queued for you, then flush again in case you've queued any requests from your event handlers - poll on the Wayland display FD as well as any other activity sources (other event queues, timers, etc) - when you wake up, dispatch your Wayland event queue as well as other relevant event sources > > Also, my taskbar is the wrong length and my background is black. Other than that, pretty cool. > > Yep, desktop-shell isn't designed to handle runtime rotation. It could be made to pretty easily by working on the client code. For your case though I'd assume something like kiosk-shell would be a much better bet. 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 git, which will be released as 10.0 in a few weeks' time. The rotation patches never got merged because we had some issues with the IIO integration in particular, but having runtime rotation tests sure would be nice, and kiosk-shell should at least be a lot easier to fix than desktop-shell, if it does even need any fixes. Cheers, Daniel<o:p></o:p> <o:p> </o:p> </div> </body> </html>