up Inquisit Language Reference

inputdevice attribute

The inputdevice attribute defines the modality used to register responses.

Member of

<defaults> <trial>

Syntax

/ inputdevice = modality

Parameters

modality One of the following values:
Value Description
keyboard Responses are defined as key-presses on the computer’s keyboard.
mouse Responses are defined as mouse clicks on target stimuli, by clicking a particular button or moving the mouse in a particular direction.
mousekey Responses are defined as the pressing of specified mouse buttons.
mouseover Responses are defined as moving the mouse over target stimuli.
touchscreen Responses are defined as touching a target stimulus presented on a monitor equipped with a touchscreen system.
speech Responses are defined as vocalizations into a microphone connected to the PC. Spoken responses are identified in real time using the speech recognition engine.
voicerecord Responses are defined as vocalizations into a microphone connected to the PC. Only latencies of spoken responses are recorded in real time, but each response is recorded as a wav file so that utterances can be identified either manually by listening to and transcribing each file, or automatically using Inquisit's Analyze Recorded Responses tool available from the Tools menu.
voicekey Responses are defined as vocalizations into a microphone connected to the PC. Only latencies of spoken responses are recorded in real time.
joystick Responses are defined as a joystick action. Joystick support is limited to Windows only.
com<n> Responses are defined as a serial port signal, where n specifies the port number (e.g., COM1, COM2, COM3, ...).
xid<n> Responses are defined as a XID protocol signal from a Cedrus Response Box on the serial port, where n optionally specifies the port number (e.g., XID1, XID2, XID3, ...). If n is omitted, Inquisit will automatically locate the XID device and connect to it. Thus, if only a single XID device is connected, the n can and should be excluded.
xid("name") Responses are defined as a XID protocol signal from a Cedrus Response Box on the serial port, where "name" specifies the device name (e.g., something like "COM3" or "COM6" on Windows, and "usbserial-00002014" or "/dev/cu.usbserial-00002014" on Mac). If a single XID device is connected to the computer, Inquisit will automatically locate and connect to the device so the name can be omitted.
eyetracker Responses are defined as gazepoints from an eyetracker configured with the eyetracker element.
lpt Responses are defined as a parallel port signal on the default status port.
lptdata Responses are defined as a parallel port signal on the default data port.
lpt<n> Responses are defined as a parallel port signal on the status port, where n specifies the port number (e.g., LPT1, LPT2, LPT3, ...).
lptdata<n> Responses are defined as a parallel port signal on the data port, where n specifies the port number (e.g., LPT1, LPT2, LPT3, ...).

Remarks

Inquisit supports a single input device per trial, although each trial in an experiment can use different input devices. The keyboard is the default input device.

Examples

The following sets the default input device for the script to voice key:

<defaults>
/ inputdevice = voicekey
</defaults>

Send comments on this topic:
Copyright Millisecond Software, LLC. All rights reserved.