<?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>topic Is resistive multi-touch a possibility with eGUI in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Is-resistive-multi-touch-a-possibility-with-eGUI/m-p/508696#M32030</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are close to launching a product that uses eGUI on a K22.&amp;nbsp; Our LCD is a resistive touchscreen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently, testing found an issue on our Home Screen.&amp;nbsp; We have 3 buttons spaced across the bottom of the screen.&amp;nbsp; If done right, testing shows that touching the leftmost and rightmost buttons at the same time can trigger the button in the middle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since we are using a voltage to interpret where touches are in the X and Y coordinate, we've used two seperate touches to effectively fake eGUI into believing that there was a single touch on that middle button.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This may just be a limit of the resistive touchscreen, but I was wondering if there might be a software solution to this problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Apr 2016 20:36:37 GMT</pubDate>
    <dc:creator>michaelsthomas</dc:creator>
    <dc:date>2016-04-15T20:36:37Z</dc:date>
    <item>
      <title>Is resistive multi-touch a possibility with eGUI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Is-resistive-multi-touch-a-possibility-with-eGUI/m-p/508696#M32030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are close to launching a product that uses eGUI on a K22.&amp;nbsp; Our LCD is a resistive touchscreen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently, testing found an issue on our Home Screen.&amp;nbsp; We have 3 buttons spaced across the bottom of the screen.&amp;nbsp; If done right, testing shows that touching the leftmost and rightmost buttons at the same time can trigger the button in the middle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since we are using a voltage to interpret where touches are in the X and Y coordinate, we've used two seperate touches to effectively fake eGUI into believing that there was a single touch on that middle button.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This may just be a limit of the resistive touchscreen, but I was wondering if there might be a software solution to this problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Apr 2016 20:36:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Is-resistive-multi-touch-a-possibility-with-eGUI/m-p/508696#M32030</guid>
      <dc:creator>michaelsthomas</dc:creator>
      <dc:date>2016-04-15T20:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: Is resistive multi-touch a possibility with eGUI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Is-resistive-multi-touch-a-possibility-with-eGUI/m-p/508697#M32031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Multitouch is not possible on resistive touchscreen.&amp;nbsp; Period.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The controller can only measure two voltages -- a proportional X, and a proportional Y.&amp;nbsp; More than one touch on the screen will just 'short out' part of the resistance, leading to an intermediate relative voltage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No magic can sort it out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Apr 2016 23:53:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Is-resistive-multi-touch-a-possibility-with-eGUI/m-p/508697#M32031</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2016-04-15T23:53:53Z</dc:date>
    </item>
  </channel>
</rss>

