<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MQX Software Solutionsのトピックegui touch calibration</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/egui-touch-calibration/m-p/185269#M3105</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am a little confused by some things on a 240x320 screen. &amp;nbsp;Our display comes oriented in portrait mode, so the built in touch calibration is misleading when following the xr, xl, yu, yd inputs from the display. &amp;nbsp;Calibrating in portrait mode causes the x and y count per pixel to be divided by the wrong value. &amp;nbsp;The code is in d4d_low.c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;snip:&lt;/P&gt;&lt;PRE&gt;...// Calculate number of (bits / pixel) * 16 for Xd4d_tchCalib.TouchScreenXBitsPerPixelx16 = (Word)((dX * 16)/(D4D_SCREEN_SIZE_LONGER_SIDE - D4DTCH_CALIB_CROSS_OFFSET * 2));// Does number of ADC bits per pixel in X seem reasonable?if (d4d_tchCalib.TouchScreenXBitsPerPixelx16 &amp;lt; ((16 * p_tchRawLimits-&amp;gt;rawDataScale) / D4D_SCREEN_SIZE_LONGER_SIDE))        {    // Calculate number of (bits / pixel) * 16 for Y    d4d_tchCalib.TouchScreenYBitsPerPixelx16 = (Word)((dY * 16)/(D4D_SCREEN_SIZE_SHORTER_SIDE - D4DTCH_CALIB_CROSS_OFFSET * 2));    // Does number of ADC bits per pixel in Y seem reasonable?    if (d4d_tchCalib.TouchScreenYBitsPerPixelx16 &amp;lt; ((16 * p_tchRawLimits-&amp;gt;rawDataScale) / D4D_SCREEN_SIZE_SHORTER_SIDE))...&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this screen we are using defaults to "portrait" the x and y are reversed. &amp;nbsp;x is the shorter side and when displaying this during calibration the text would be reversed as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This isn't a hard fix, just commenting that it might be helpful to make this more configurable in the user_cfg.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Oct 2020 09:36:05 GMT</pubDate>
    <dc:creator>Toe</dc:creator>
    <dc:date>2020-10-29T09:36:05Z</dc:date>
    <item>
      <title>egui touch calibration</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/egui-touch-calibration/m-p/185269#M3105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am a little confused by some things on a 240x320 screen. &amp;nbsp;Our display comes oriented in portrait mode, so the built in touch calibration is misleading when following the xr, xl, yu, yd inputs from the display. &amp;nbsp;Calibrating in portrait mode causes the x and y count per pixel to be divided by the wrong value. &amp;nbsp;The code is in d4d_low.c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;snip:&lt;/P&gt;&lt;PRE&gt;...// Calculate number of (bits / pixel) * 16 for Xd4d_tchCalib.TouchScreenXBitsPerPixelx16 = (Word)((dX * 16)/(D4D_SCREEN_SIZE_LONGER_SIDE - D4DTCH_CALIB_CROSS_OFFSET * 2));// Does number of ADC bits per pixel in X seem reasonable?if (d4d_tchCalib.TouchScreenXBitsPerPixelx16 &amp;lt; ((16 * p_tchRawLimits-&amp;gt;rawDataScale) / D4D_SCREEN_SIZE_LONGER_SIDE))        {    // Calculate number of (bits / pixel) * 16 for Y    d4d_tchCalib.TouchScreenYBitsPerPixelx16 = (Word)((dY * 16)/(D4D_SCREEN_SIZE_SHORTER_SIDE - D4DTCH_CALIB_CROSS_OFFSET * 2));    // Does number of ADC bits per pixel in Y seem reasonable?    if (d4d_tchCalib.TouchScreenYBitsPerPixelx16 &amp;lt; ((16 * p_tchRawLimits-&amp;gt;rawDataScale) / D4D_SCREEN_SIZE_SHORTER_SIDE))...&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this screen we are using defaults to "portrait" the x and y are reversed. &amp;nbsp;x is the shorter side and when displaying this during calibration the text would be reversed as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This isn't a hard fix, just commenting that it might be helpful to make this more configurable in the user_cfg.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2020 09:36:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/egui-touch-calibration/m-p/185269#M3105</guid>
      <dc:creator>Toe</dc:creator>
      <dc:date>2020-10-29T09:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: eGUI touch calibration</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/egui-touch-calibration/m-p/185270#M3106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;you absolutely right, thank you for the feedback.&lt;BR /&gt;&lt;BR /&gt;By the way three days ago I found some issue because I start test on 800x480 pixels LCD in portrait mode.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Dec 2011 16:58:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/egui-touch-calibration/m-p/185270#M3106</guid>
      <dc:creator>Gargy</dc:creator>
      <dc:date>2011-12-01T16:58:13Z</dc:date>
    </item>
  </channel>
</rss>

