<?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 Multitouch in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/multitouch/m-p/440758#M5331</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="line-height: 107%; font-family: 'Calibri',sans-serif; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;We at Esri Sweden are currently developing with Runtime for .NET for our Defence customers and they are using&lt;BR /&gt;multitouch screens. We are going to purchase such a screen ourself for testing&lt;BR /&gt;and demo purposes. Question is if someone have worked with .NET SDK on multitouch&lt;BR /&gt;and have recommendations on what to think about. Is the SDK working better on&lt;BR /&gt;certain types or brands? Maximum and minimum numbers of touchpoints? Things to consider regarding 3D?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="line-height: 107%; font-family: 'Calibri',sans-serif; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Do you in the Runtime .NET-team at Esri Inc have any inputs in this matter? Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Dec 2014 09:23:14 GMT</pubDate>
    <dc:creator>JanneEriksson</dc:creator>
    <dc:date>2014-12-16T09:23:14Z</dc:date>
    <item>
      <title>Multitouch</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/multitouch/m-p/440758#M5331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="line-height: 107%; font-family: 'Calibri',sans-serif; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;We at Esri Sweden are currently developing with Runtime for .NET for our Defence customers and they are using&lt;BR /&gt;multitouch screens. We are going to purchase such a screen ourself for testing&lt;BR /&gt;and demo purposes. Question is if someone have worked with .NET SDK on multitouch&lt;BR /&gt;and have recommendations on what to think about. Is the SDK working better on&lt;BR /&gt;certain types or brands? Maximum and minimum numbers of touchpoints? Things to consider regarding 3D?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="line-height: 107%; font-family: 'Calibri',sans-serif; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Do you in the Runtime .NET-team at Esri Inc have any inputs in this matter? Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 09:23:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/multitouch/m-p/440758#M5331</guid>
      <dc:creator>JanneEriksson</dc:creator>
      <dc:date>2014-12-16T09:23:14Z</dc:date>
    </item>
  </channel>
</rss>

