Millisecond Forums

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

Can you please private message me the full log? The excerpt is missing some crucial technical information

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

Can you please private message me the full log? The excerpt is missing some crucial technical information

Sorry about that. Just dm'ed you the full log.

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

Can you please private message me the full log? The excerpt is missing some crucial technical information

Sorry about that. Just dm'ed you the full log.

Thank you. We'll investigate and I'll post an update here once I know more

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

Can you please private message me the full log? The excerpt is missing some crucial technical information

Sorry about that. Just dm'ed you the full log.

Thank you. We'll investigate and I'll post an update here once I know more

So far, we're not reproducing this on any of our Windows Integrated Touch devices. The detection flags in the full log look normal, i.e. the touch screen and its capabilities are detected, and the flag values are identical to what we're seing on our devices, where touch input works as expected. The output from the test code posted upthread shows the tocuh screen being detected at runtime as well, so it's strange that input should fail.

Questions:
- Did touch input ever work, with any script, under 7.1.3 on your Surface Go? That would include scripts expecting keyboard input, whch should display on-screen buttons when the keyboard is detached.
- Does the problem persist after a full system reboot? I'm wondering whether some in.memory module got into a faulty state and isn't being reloaded properly.

+x

 

Dave - 10/9/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

+x

 

Dave - 10/8/2025

+x

 

CraigM - 10/8/2025

Hi Dave.

I am finding that a script with the default input device set to "touchscreen" is not working properly in Inquisit 7, but the exact same script does work in Inquisit 6.

When I say "not working properly," I mean the script does run, but the touchscreen inputs do not register. Tapping on the response stimulus does nothing. However it does work in Inquisit 6.

I have tried putting the inputdevice attribute within the trial element, and that doesn't change it. I have also tried changing input device to mouse, but get the same result.

I am attaching a basic demo script to demonstrate this.

I am using a Surface Go running Windows 10.

Is this just a case of me needing to write the script differently in Inquisit 7, or is there something else going on?

Happy to provide any other information if you need it. Thank you.

     ~Craig

Could you please:
(1) Provide the exact Inquisit 7 version you have installed? Also, if the installation is not up to date, please install the latest release and confirm that the issue persists.
(2) Provide the application log.
Tools -> View Log File if you are using Inquisit Lab.
Tap Show Application Log on the Browse Tab if you are using Inquisit Web.
(3) What's the on-screen output of the following code:

<text myText>
/ items = ("
<%computer.os%> (<%computer.osMajorVersion%>.<%computer.osMinorVersion%>)
<%display.width%> * <%display.height%> @ <%display.refreshRate%>Hz
Scale <%display.screenScale%>
<%computer.availableMemory%> / <%computer.memory%>
Touch screen detected: <%computer.touch%>
Keyboard detected: <%computer.hasKeyboard%>
")
/ fontStyle = ("Arial", 2.08%, false, false, false, false, 5, 1)
</text>

<trial myTrial>
/ screenCapture = true
/ preTrialPause = 500
/ stimulusTimes = [1=myText]
/ validResponse = (" ")
/ timeout = 10000
</trial>

<block myBlock>
/ trials = [1=myTrial]
</block>

<expt myExpt>
/ blocks = [1=myBlock]
</expt>

1. Version: I'm using version 7.1.3 64bit (build 8827) on the Surface Go. I downloaded it today.

2.  Log: I am attaching the log for running the script once on Inquisit Lab. I hope it's ok that I attached it as a .txt file and not .log; I did this so I could delete earlier information from the log, some of which included personal information.

3. Output:

win10 (10.0)
1200 * 765.984252 @ 59.90Hz
Scale 1.5
4062644 / 8270292
Touch screen detected: 1
Keyboard detected: 1

The numerator in the fourth row is different each time I run it.

Can you please private message me the full log? The excerpt is missing some crucial technical information

Sorry about that. Just dm'ed you the full log.

Thank you. We'll investigate and I'll post an update here once I know more

So far, we're not reproducing this on any of our Windows Integrated Touch devices. The detection flags in the full log look normal, i.e. the touch screen and its capabilities are detected, and the flag values are identical to what we're seing on our devices, where touch input works as expected. The output from the test code posted upthread shows the tocuh screen being detected at runtime as well, so it's strange that input should fail.

Questions:
- Did touch input ever work, with any script, under 7.1.3 on your Surface Go? That would include scripts expecting keyboard input, whch should display on-screen buttons when the keyboard is detached.
- Does the problem persist after a full system reboot? I'm wondering whether some in.memory module got into a faulty state and isn't being reloaded properly.

Two more questons to help narrow this down:
(1) Could you please run the attached script and private message me the resulting IQDAT file? If touching the text does not work, please touch anywhere on the canvas. This should tell us whether the coordinates we're getting from the touch screen are what we expect them to be.
(2) Could you let us know the exact Surface Go model?

Hi Dave.

I apologize for not being able to reply until now.

My Surface Go updated Windows this morning and now the touch inputs are working. This is amateur and I'm embarrassed; that should have been the second thing I tried (after turning it off and on again). I guess I just didn't think of it because the device was offline at the time, so I wouldn't have been able to download an update. But I should have waited to post until I had gotten to do an update.

For the record, prior to me running the Windows update: no other touchscreen script worked, the keyboard inputs did not appear when running a touchscreen script (just a blank white space where the on-screen keys should have been), and I replicated the problem on another Surface Go (we have a set). So it looks like it was a problem with a specific version of Windows, although I don't know why Inquisit 6 was working fine on that older Windows.

Anyway, I'm sorry for wasting your time. Next time I'll remember to do the obvious stuff first.

Thank you.

     ~Craig

+x

 

CraigM - 10/9/2025

Hi Dave.

I apologize for not being able to reply until now.

My Surface Go updated Windows this morning and now the touch inputs are working. This is amateur and I'm embarrassed; that should have been the second thing I tried (after turning it off and on again). I guess I just didn't think of it because the device was offline at the time, so I wouldn't have been able to download an update. But I should have waited to post until I had gotten to do an update.

For the record, prior to me running the Windows update: no other touchscreen script worked, the keyboard inputs did not appear when running a touchscreen script (just a blank white space where the on-screen keys should have been), and I replicated the problem on another Surface Go (we have a set). So it looks like it was a problem with a specific version of Windows, although I don't know why Inquisit 6 was working fine on that older Windows.

Anyway, I'm sorry for wasting your time. Next time I'll remember to do the obvious stuff first.

Thank you.

     ~Craig

Thanks for the update. The plausible explanation is that the update included newer touch screen drivers that either fixed some bugs and/or improved compatibility with newer APIs. We'll close this bug for now, but do let us know if the issue resurfaces.