1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
function [event, nremaining] = KbEventGet(deviceIndex, maxWaitTimeSecs)
% [event, nremaining] = KbEventGet([deviceIndex][, maxWaitTimeSecs=0])
%
% Return oldest pending event, if any, in return argument 'event', and the
% remaining number of recorded events in the event buffer of a keyboard
% queue in the return argument 'nremaining'.
%
% By default, the event buffer of the default keyboard queue is checked,
% but you can specify 'deviceIndex' to check the buffer of the queue
% associated with 'deviceIndex'.
%
% KbEventGet() will wait up to 'maxWaitTimeSecs' seconds for at least one
% event to show up before it gives up. By default, it doesn't wait but just
% gives up if there aren't any events queued at time of invocation.
%
% 'event' is either empty if there aren't any events available, or it is a
% struct with information about the keyboard event. The returned event
% struct currently contains the following fields:
%
% 'Keycode' = The KbCheck / KbName style keycode of the key or button that
% triggered this event.
%
% 'Time' = The GetSecs time of when the event was received.
%
% 'Pressed' = 1 for a key press event, 0 for a key release event.
%
% 'CookedKey' = Keycode translated into a GetChar() style Unicode character code.
% Or zero if key does not have a corresponding character. Or -1 if mapping
% is unsupported for given event.
%
% A note on international keyboards: Non US keyboards with a different layout,
% e.g., german keyboards, may have keys that do not exist on US keyboards, e.g.,
% german umlauts like ö, ä, ü, ß. How such non-ASCII characters are translated
% into proper 'CookedKey' key codes is dependent on the language locale setup of
% your operating system for the keyboard. There is some potential for confusion
% there and it could happen that if Psychtoolbox misdetects the chosen keyboard
% layout, it will return such keys with the wrong character code. E.g., the ö key
% of a german keyboard may map to a ; key if german layout is misdetected as US
% layout. If this happens, try to select the proper keyboard layout in the GUI
% setup tools of your operating system, "clear all" and then retry. On Linux/X11
% it has been observed that this settings selected via GUI tools is not always
% respected, e.g., on the KDE and GNOME desktop environment. In this case, use
% of the terminal command line tool "setxkbmap" managed to enforce use of the
% correct keyboard layout for key -> char translation. E.g., "setxkbmap -layout de"
% to select a german keyboard layout. Obviously you could call
% system('setxkbmap -layout de'); from within your script to achieve this effect.
%
% Psychtoolbox will return mapped keys in 'CookedKey' as double() values, encoding
% Unicode character codes in the UTF-16 (on MS-Windows) or UTF-32 (Linux, macOS)
% encoding and code range. This currently works splendidly with Matlab, but current
% versions of GNU/Octave (as of version 5.1) are not really unicode capable and can
% only deal with UTF-8 encoded strings in a limited fashion. This means that if you
% use Octave, you can receive proper 'CookedKey' UTF-32 unicode characters from
% international keyboards, you can manipulate the double() values in your script,
% but Octave's string processing functions, or even printing such characters to
% the Octave command window via disp() or fprintf() will likely give wrong behaviour.
% This is a design limitation of current Octave, so you will have to work around it.
%
% Keyboard event buffers are a different way to access the information
% collected by keyboard queues. Before you can use an event buffer you
% always must create its "parent keyboard queue" via KbQueueCreate() and
% call KbQueueStart() to enable key event recording. See "help
% KbQueueCreate" etc. on how to do this.
%
% _________________________________________________________________________
%
% See also: KbQueueCreate, KbQueueStart, KbQueueStop, KbQueueCheck,
% KbQueueWait, KbQueueFlush, KbQueueRelease
% 21.5.2012 mk Wrote it.
if nargin < 1
deviceIndex = [];
end
% Try to check if keyboard queue for 'deviceIndex' is reserved for our exclusive use:
if ~KbQueueReserve(3, 2, deviceIndex) && KbQueueReserve(3, 1, deviceIndex)
if isempty(deviceIndex)
deviceIndex = NaN;
end
error('Keyboard queue for device %i already in use by GetChar() et al. Use of GetChar and keyboard queues is mutually exclusive!', deviceIndex);
end
if ~KbQueueReserve(3, 2, deviceIndex)
if isempty(deviceIndex)
deviceIndex = NaN;
end
error('Keyboard queue for device %i not yet created. KbQueueCreate() it first!\n', deviceIndex);
end
if nargin < 2
maxWaitTimeSecs = [];
end
[event, nremaining] = PsychHID('KbQueueGetEvent', deviceIndex, maxWaitTimeSecs);
return;
|
