Millisecond Forums

That bar will only be displayed on touch-enabled devices: This makes it possible to complete a script that's been designed for keyboard input on devices that may not have a physical keyboard without having to make any changes to the script (i.e. define a different /inputdevice, etc.). The bar will not be displayed on devices that do not support touchscreen-input.

The response options displayed on the bar during the trials should reflect what is specified in the respective <trial> elements' /validresponse and/or /correctresponse settings. I take it that you're seeing a different result. Could you detail

(1) What you specified in the relevant /validresponse attributes, and
(2) What the mismatch is with respect to the different language keyboards you are using (also: which language layout do those keyboards have?)?

Thanks.

Hi Dave,

Thanks for the quick response.

Regarding your questions:
1) Here is what we're using. We're using the actual key codes rather than characters because the trial didn't seem to accept unicode correctly
/ validresponse = (18, 23)
/ correctresponse = (18)

2) We're running the tests in Russian and Ukrainian. In both cases, the equivalent of (E,I) would be (У,Ш)

If there is a way to use the Cyrillic characters rather than the key codes, that might be the best way to go so that the bar takes the correct values.

On the question on whether the bar should be there at all, we discovered it in a Lenovo Thinkpad X240 with no touch screen capability.

Thanks again,

Mario

Regarding the X240: I have seen ThinkPad factory installs that had touchscreen drivers installed even when the system doesn't actually have a touchscreen. You can if this is the case check via the device manager and -- if so -- disable or remove the driver: http://www.thewindowsclub.com/disable-touch-screen-windows-10 (the steps for other Windows versions, e.g. 7 or 8, are virtually identical).

Regarding the keyboard / language issue:
(1) Is the computer's display language actually set to Russian or Ukrainian respectively?
(2) What is the system locale set to?
(3) What is the default input language set to (cf. "Text Services and Input Languages" in the Windows control panel)?

Thanks!

Just thought I'd join in on this thread as I was logging into ask a similar question.

I also think this is annoying, and it would be great to be able to turn it off.  I run a dell laptop with a docking station at work, and with Inquisit 5, this bar shows up when I run scripts, even though I have hardware connected.  The testing machines we use also have hardware connected but because they are also touchscreen, the bar shows up.  Not only is it annoying, it looks bad too.

On the windows tablets we run for testing in the clinic, I run a series of reaction time tasks and other speed of processing tasks, programmed in inquisit 4, using stimulus responses for input (and mouse as the response attribute).  It worked fine, other than the occasional swipe from the right which initiates the windows side bar. I was hoping V5 would somehow lock this and not allow it to happen.  This is probably the only issue preventing me from upgrading to be honest.

Inquisit 5 also crashes for me on an Asus Windows 8 device. How can I get the error log to send this through?

Thanks for the feedback. I will add those suggestions to our feature tracker.

As for the crashes on the ASUS tablet:
(1) If the Inquisit 5 version the tablet is not the latest release, please install that and check if the crashing persists (the current release is 5.0.1.0).
(2) The Windows crash report will be available via the event viewer: https://www.digitalmastersmag.com/magazine/tip-of-the-day-how-to-find-crash-logs-on-windows-8/
(3) Inquisit also keeps its own log file of technical information, which *may* be helpful. It is accessible via Tools -> View Log File...

I should add that the approach you used under Inquisit 4 should still work unchanged under Inquisit 5, i.e., using /inputdevice = touchscreen or /inputdevice = mouse in the scripts intended for use on the clinic tablets. (I'm not certain offhand if the Windows side bar can be blocked entirely, reliably and safely, but I will add that to the list as well.)

Hi Dave, 

I'm having a fairly similar problem with my relatively standard IAT script. I'm testing it on my personal touchscreen laptop (with full keyboard) and even though the input is set to keyboard it will not accept keyboard responses, only via using the touchscreen. As you know speed is critical for the IAT and touchscreen just won't do for us.

Is there any way to disable the bottom bar from popping up on touchscreen laptops? (We don't need people to be able to use iPads or other similar tablet devices so that's not an issue.) Unfortunately we can't just disable the windows driver because we'll be using web and it won't be possible to do on all of our participants' computers. If it cannot be disabled, is there a way that ensures it accepts keyboard responses on touchscreens? Or other suggestions you have would be greatly appreciated.

Thank you!
Carli

Carli,
Inquisit should detect your keyboard and hide the response bar. Are you running the latest version of Inquisit Lab (5.0.7)? If not, try updating and see if this fixes the issue - we fixed a similar bug a while ago.
If that doesn't help, can you tell us what kind of laptop you have? Is this a detachable keyboard, or is it built into the laptop? Blue tooth or wired? 
Thanks,
Sean

Hi Sean,

Thanks for getting back. Yes, I'm running the latest version. I'm actually testing with the latest version of web (5.0.7.0), not lab, as I'm about ready to launch. It's not detecting my keyboard whatsoever. I have a Lenovo Yoga 2 Pro, the keyboard is completely built in. I'm less concerned about this working on my computer though and more about random participants computers.

Carli

Hi Carli,
This doesn't appear to be a widespread problem as we aren't hearing similar bug reports from other customers (aside the one I mentioned that we fixed a while ago). Possibly the issue is unique to the configuration settings on your particular laptop. 
To help us troubleshoot, \would you be willing to try this on a special release of Inquisit Lab that logs various parameters of your hardware so that we can see more closely where the failure is? If so, please email me at inquisit@millisecond.com and I can send you a link and instructions.

Thanks,
Sean