﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Millisecond Forums » Millisecond Forums » Inquisit 5  » Trail Making Test with Windows Tablet?</title><generator>InstantForum 2017-1 Final</generator><description>Millisecond Forums</description><link>https://forums.millisecond.com/</link><webMaster>Millisecond Forums</webMaster><lastBuildDate>Thu, 09 Apr 2026 20:10:53 GMT</lastBuildDate><ttl>20</ttl><item><title>Trail Making Test with Windows Tablet?</title><link>https://forums.millisecond.com/Topic21793.aspx</link><description>Hello,&lt;br/&gt;&lt;br/&gt;We're having a bit of an issue still with the Trail Making Test (TMT) when running on a Windows Tablet. Specifically, we've had some "wonkiness" when asking participants to draw using their finger/stylus - the traced line will dart around, not trace at times, not register taps/touches when participants clearly meant to go over the appropriate number/letter, etc. Enlarging the test area and running it in "portrait" mode helps to some extent, but not enough to where we're extremely confident in the error counts we're getting (i.e., false errors). One thing that seems odd is that we noticed the inputdevice attribute is defaulted to mouse, which seems to make sense - we never seem to be getting these errors on a desktop platform. &lt;br/&gt;&lt;br/&gt;&lt;br/&gt;My question is - if we set the inputdevice or validresponse to "touch" somehow, would that fix some of this wonkiness? I can't help but feel that part of the problem is that the tablet thinks the participant is tracing using a mouse and this is causing some idiosyncrasies in the tracing (and therefore, registering which numbers/letters are hit). Thoughts?&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;&lt;br/&gt;-`-Tim</description><pubDate>Fri, 09 Jun 2017 09:42:35 GMT</pubDate><dc:creator>drtb</dc:creator></item><item><title>RE: Trail Making Test with Windows Tablet?</title><link>https://forums.millisecond.com/Topic21807.aspx</link><description>&lt;div data-id="21805" class="if-quote-wrapper" unselectable="on" data-guid="1497026311919"&gt;&lt;a class="quote-para" unselectable="on" style="display: none;" href="#" data-id="21805" title="Move Cursor Below" contenteditable="false"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a class="quote-delete" unselectable="on" style="display: none;" href="#" data-id="21805" title="Delete Quote" contenteditable="false"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span unselectable="on" class="quote-markup"&gt;[quote]&lt;/span&gt;&lt;div unselectable="on" class="if-quote-header" contenteditable="false"&gt;&lt;div unselectable="on" class="if-quote-toggle-wrapper"&gt;&lt;a class="if-quote-toggle quote-link" href="#" data-id="21805" title=" "&gt;&lt;/a&gt;&lt;/div&gt;&lt;span unselectable="on" class="quote-markup"&gt;[b]&lt;/span&gt;drtb - Friday, June 9, 2017&lt;span unselectable="on" class="quote-markup"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21805"&gt;&lt;div class="if-quote-message-margin"&gt;&lt;div class="if-quote-wrapper" unselectable="on" data-id="21796" data-guid="1497026311919"&gt;&lt;a title="Move Cursor Below" class="quote-para" style="display: none;" href="#" unselectable="on" data-id="21796" contenteditable="false"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a title="Delete Quote" class="quote-delete" style="display: none;" href="#" unselectable="on" data-id="21796" contenteditable="false"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span class="quote-markup" unselectable="on"&gt;[quote]&lt;/span&gt;&lt;div class="if-quote-header" unselectable="on" contenteditable="false"&gt;&lt;div class="if-quote-toggle-wrapper" unselectable="on"&gt;&lt;a title=" " class="if-quote-toggle quote-link" href="#" data-id="21796"&gt;&lt;/a&gt;&lt;/div&gt;&lt;span class="quote-markup" unselectable="on"&gt;[b]&lt;/span&gt;Dave - Wednesday, June 7, 2017&lt;span class="quote-markup" unselectable="on"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21796"&gt;&lt;div class="if-quote-message-margin"&gt;&lt;div class="if-quote-wrapper" data-guid="1497026311919" unselectable="on" data-id="21793"&gt;&lt;a title="Move Cursor Below" class="quote-para" style="display: none;" href="#" unselectable="on" data-id="21793" contenteditable="false"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a title="Delete Quote" class="quote-delete" style="display: none;" href="#" unselectable="on" data-id="21793" contenteditable="false"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span class="quote-markup" unselectable="on"&gt;[quote]&lt;/span&gt;&lt;div class="if-quote-header" unselectable="on" contenteditable="false"&gt;&lt;div class="if-quote-toggle-wrapper" unselectable="on"&gt;&lt;a title=" " class="if-quote-toggle quote-link" href="#" data-id="21793"&gt;&lt;/a&gt;&lt;/div&gt;&lt;span class="quote-markup" unselectable="on"&gt;[b]&lt;/span&gt;drtb - Wednesday, June 7, 2017&lt;span class="quote-markup" unselectable="on"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21793"&gt;&lt;div class="if-quote-message-margin"&gt;Hello,&lt;br/&gt;&lt;br/&gt;We're having a bit of an issue still with the Trail Making Test (TMT) when running on a Windows Tablet. Specifically, we've had some "wonkiness" when asking participants to draw using their finger/stylus - the traced line will dart around, not trace at times, not register taps/touches when participants clearly meant to go over the appropriate number/letter, etc. Enlarging the test area and running it in "portrait" mode helps to some extent, but not enough to where we're extremely confident in the error counts we're getting (i.e., false errors). One thing that seems odd is that we noticed the inputdevice attribute is defaulted to mouse, which seems to make sense - we never seem to be getting these errors on a desktop platform. &lt;br/&gt;&lt;br/&gt;&lt;br/&gt;My question is - if we set the inputdevice or validresponse to "touch" somehow, would that fix some of this wonkiness? I can't help but feel that part of the problem is that the tablet thinks the participant is tracing using a mouse and this is causing some idiosyncrasies in the tracing (and therefore, registering which numbers/letters are hit). Thoughts?&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;&lt;br/&gt;-`-Tim&lt;a class="if-quote-goto quote-link" href="#" data-id="21793"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;I don't think that changing /inputdevice to touchscreen will necessarily improve matters, but that should not keep you from giving it a try nonetheless.&lt;br/&gt;More likely, the difference you're seeing is simply due to that fact that different input modalities -- on a hardware-level -- have different properties and measurement error associated with them. I.e. some touch screens will be much less sensitive and sample at a lower rate than a typical mouse.&lt;br/&gt;&lt;a class="if-quote-goto quote-link" href="#" data-id="21796"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;No worries, that's about what I had figured. Any way to make the circles a little bit bigger on the screen - and therefore, more forgiving for registering "hits" on a touch screen? Tried enlarging the photos themselves but that didn't do much in terms of seeing them enlarged during the test itself. &lt;br/&gt;&lt;a class="if-quote-goto quote-link" href="#" data-id="21805"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;You need to change the /size of the various &amp;lt;picture&amp;gt; elements throughout the script. I.e., taking the 1st script -- samplea.iqx -- as example, change&lt;br/&gt;&lt;br/&gt;&amp;lt;picture SA1pic&amp;gt;&lt;br/&gt;/ items = ("1.jpg")&lt;br/&gt;&lt;strong&gt;/ size = (5%, 5%)&lt;/strong&gt;&lt;br/&gt;/ position = (53%, 20%)&lt;br/&gt;/ erase = false&lt;br/&gt;&amp;lt;/picture&amp;gt;&lt;br/&gt;&lt;br/&gt;to, say, &lt;br/&gt;&lt;br/&gt;&amp;lt;picture SA1pic&amp;gt;&lt;br/&gt;/ items = ("1.jpg")&lt;br/&gt;&lt;strong&gt;/ size = (8%, 8%)&lt;/strong&gt;&lt;br/&gt;/ position = (53%, 20%)&lt;br/&gt;/ erase = false&lt;br/&gt;&amp;lt;/picture&amp;gt;&lt;br/&gt;&lt;br/&gt;and so forth.&lt;br/&gt;</description><pubDate>Fri, 09 Jun 2017 09:42:35 GMT</pubDate><dc:creator>Dave</dc:creator></item><item><title /><link>https://forums.millisecond.com/Topic21805.aspx</link><description>&lt;div class="if-quote-wrapper" unselectable="on" data-id="21796"&gt;&lt;a title="Move Cursor Below" class="quote-para" style="display: none;" contenteditable="false" href="#" unselectable="on" data-id="21796"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a title="Delete Quote" class="quote-delete" style="display: none;" contenteditable="false" href="#" unselectable="on" data-id="21796"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span class="quote-markup" unselectable="on"&gt;[quote]&lt;/span&gt;&lt;div class="if-quote-header" contenteditable="false" unselectable="on"&gt;&lt;div class="if-quote-toggle-wrapper" unselectable="on"&gt;&lt;a title=" " class="if-quote-toggle quote-link" href="#" data-id="21796"&gt;&lt;/a&gt;&lt;/div&gt;&lt;span class="quote-markup" unselectable="on"&gt;[b]&lt;/span&gt;Dave - Wednesday, June 7, 2017&lt;span class="quote-markup" unselectable="on"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21796"&gt;&lt;div class="if-quote-message-margin"&gt;&lt;div class="if-quote-wrapper" data-guid="1496869285195" unselectable="on" data-id="21793"&gt;&lt;a title="Move Cursor Below" class="quote-para" style="display: none;" contenteditable="false" href="#" unselectable="on" data-id="21793"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a title="Delete Quote" class="quote-delete" style="display: none;" contenteditable="false" href="#" unselectable="on" data-id="21793"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span class="quote-markup" unselectable="on"&gt;[quote]&lt;/span&gt;&lt;div class="if-quote-header" contenteditable="false" unselectable="on"&gt;&lt;div class="if-quote-toggle-wrapper" unselectable="on"&gt;&lt;a title=" " class="if-quote-toggle quote-link" href="#" data-id="21793"&gt;&lt;/a&gt;&lt;/div&gt;&lt;span class="quote-markup" unselectable="on"&gt;[b]&lt;/span&gt;drtb - Wednesday, June 7, 2017&lt;span class="quote-markup" unselectable="on"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21793"&gt;&lt;div class="if-quote-message-margin"&gt;Hello,&lt;br/&gt;&lt;br/&gt;We're having a bit of an issue still with the Trail Making Test (TMT) when running on a Windows Tablet. Specifically, we've had some "wonkiness" when asking participants to draw using their finger/stylus - the traced line will dart around, not trace at times, not register taps/touches when participants clearly meant to go over the appropriate number/letter, etc. Enlarging the test area and running it in "portrait" mode helps to some extent, but not enough to where we're extremely confident in the error counts we're getting (i.e., false errors). One thing that seems odd is that we noticed the inputdevice attribute is defaulted to mouse, which seems to make sense - we never seem to be getting these errors on a desktop platform. &lt;br/&gt;&lt;br/&gt;&lt;br/&gt;My question is - if we set the inputdevice or validresponse to "touch" somehow, would that fix some of this wonkiness? I can't help but feel that part of the problem is that the tablet thinks the participant is tracing using a mouse and this is causing some idiosyncrasies in the tracing (and therefore, registering which numbers/letters are hit). Thoughts?&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;&lt;br/&gt;-`-Tim&lt;a class="if-quote-goto quote-link" href="#" data-id="21793"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;I don't think that changing /inputdevice to touchscreen will necessarily improve matters, but that should not keep you from giving it a try nonetheless.&lt;br/&gt;More likely, the difference you're seeing is simply due to that fact that different input modalities -- on a hardware-level -- have different properties and measurement error associated with them. I.e. some touch screens will be much less sensitive and sample at a lower rate than a typical mouse.&lt;br/&gt;&lt;a class="if-quote-goto quote-link" href="#" data-id="21796"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;No worries, that's about what I had figured. Any way to make the circles a little bit bigger on the screen - and therefore, more forgiving for registering "hits" on a touch screen? Tried enlarging the photos themselves but that didn't do much in terms of seeing them enlarged during the test itself. &lt;br/&gt;</description><pubDate>Fri, 09 Jun 2017 08:56:23 GMT</pubDate><dc:creator>drtb</dc:creator></item><item><title>RE: Trail Making Test with Windows Tablet?</title><link>https://forums.millisecond.com/Topic21796.aspx</link><description>&lt;div data-id="21793" class="if-quote-wrapper" unselectable="on" data-guid="1496869285195"&gt;&lt;a class="quote-para" unselectable="on" style="display: none;" href="#" data-id="21793" title="Move Cursor Below" contenteditable="false"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a class="quote-delete" unselectable="on" style="display: none;" href="#" data-id="21793" title="Delete Quote" contenteditable="false"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span unselectable="on" class="quote-markup"&gt;[quote]&lt;/span&gt;&lt;div unselectable="on" class="if-quote-header" contenteditable="false"&gt;&lt;div unselectable="on" class="if-quote-toggle-wrapper"&gt;&lt;a class="if-quote-toggle quote-link" href="#" data-id="21793" title=" "&gt;&lt;/a&gt;&lt;/div&gt;&lt;span unselectable="on" class="quote-markup"&gt;[b]&lt;/span&gt;drtb - Wednesday, June 7, 2017&lt;span unselectable="on" class="quote-markup"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-21793"&gt;&lt;div class="if-quote-message-margin"&gt;Hello,&lt;br/&gt;&lt;br/&gt;We're having a bit of an issue still with the Trail Making Test (TMT) when running on a Windows Tablet. Specifically, we've had some "wonkiness" when asking participants to draw using their finger/stylus - the traced line will dart around, not trace at times, not register taps/touches when participants clearly meant to go over the appropriate number/letter, etc. Enlarging the test area and running it in "portrait" mode helps to some extent, but not enough to where we're extremely confident in the error counts we're getting (i.e., false errors). One thing that seems odd is that we noticed the inputdevice attribute is defaulted to mouse, which seems to make sense - we never seem to be getting these errors on a desktop platform. &lt;br/&gt;&lt;br/&gt;&lt;br/&gt;My question is - if we set the inputdevice or validresponse to "touch" somehow, would that fix some of this wonkiness? I can't help but feel that part of the problem is that the tablet thinks the participant is tracing using a mouse and this is causing some idiosyncrasies in the tracing (and therefore, registering which numbers/letters are hit). Thoughts?&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;&lt;br/&gt;-`-Tim&lt;a class="if-quote-goto quote-link" href="#" data-id="21793"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;I don't think that changing /inputdevice to touchscreen will necessarily improve matters, but that should not keep you from giving it a try nonetheless.&lt;br/&gt;More likely, the difference you're seeing is simply due to that fact that different input modalities -- on a hardware-level -- have different properties and measurement error associated with them. I.e. some touch screens will be much less sensitive and sample at a lower rate than a typical mouse.&lt;br/&gt;</description><pubDate>Wed, 07 Jun 2017 14:04:51 GMT</pubDate><dc:creator>Dave</dc:creator></item></channel></rss>