xMachine/todo.txt at master · Feri73/xMachine · GitHub

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
experiment classses (signals, state, transitions) can have public proeperties and removed run function

you cannot do this: objectMap(object).getId but can do this: objectMap(object).getId(). Solve this problem (change the way I handle objectMap and VariableSpace)

copy variables when passing to signals
copy signals when apssing to states

//initialize shaerdmemory.* (i mean they are equal to variablespaces e.g.)

//experiment parameters (both existence and saving)

XX a function for specifying nextTrial (in Experiment) which is called by stateHandlers (by user)

force to use VariableSpace as sharedMemory.outputSignals

init state goes to experiment and experiment runs it (to simplify the experiment's state machine)

//save state changes!

dataviewer messages

make objectmap and variablesspace work in situations like this: inputs.tracker(EVenttype.StartBlink)

support dummy mode for eyelink (aother eyetracker)

are "message"s in Eyelink essential??

read programming manual of eyelink

have possibility that PTBAdaptor do not clear previous frame, or does not sync, etc.

StateMachine.compile should become cleaner

//storage module
time module

design for two display adaptors

audio adaptor

stimuli or stimulus?

module for states that do not repeat (are not continuous)

add module to have a white rectangle to use in photocell

allow null handler in storage (data or state handler)

//parameters

read comments

better desing for eyelink.nexttrial usage

add father for rectangle, circlt, etc.

do sth so that tagging of eyelink acts as storage==>with !V commands

use the flip command like what amin did

have extra useful part for things like fixation class, audio adaptor, general display adaptor, timedstate, etc.