Hello Tina,
I would be happy to help. For the sake of clarity, I have numbered my responses to match your questions.
1) This is definitely possible but requires a bit more InLine script than the original TETFixedPositionAOI sample. In short, you'll basically have to make a duplicate of the SaveGazeData subroutine in the User Script. One copy of this script will be for your Practical block and the other is for your testing block. Then, in your SaveGazeData InLine objects (of which there will need to be two), just make sure you are referencing the correct subroutine in the User Script.
2) I would be happy to explain the TETWaitForFixation Package call. I've actually done quite a lot of testing on this call when I was at PST. Your assumption of the functions of this call are 100% correct. Its purpose is to basically pause the experiment on a single fixation point (usually a SlideText sub-object) until the participant looks at it for a pre-defined amount of time or terminated by a keyboard or mouse press to move on. While it's a handy little package call, it has a few things that NEED to be in place in order for it to work as intended. They are as follows:
a) It can only be used in conjunction with a Slide object (that is named in the first parameter of the Package Call (usually called Fixation)
b) The Slide sub-object on which participants will be fixating needs to be called Fixation. (this is usually a SlideText sub-object)
c) The Slide object needs a Duration of 0
d) The Slide object needs a Keyboard Input Mask with an Allowable set to {ANY}, a Time Limit set to "(until feedback)" and an End Action set to "(none)"
3) The AOIs in E-Prime are actually all calculated in the SaveGazeData InLine object at the end of the procedure (after the trial has already run). Generally, the easiest way for E-Prime to calculate AOIs is by using the strHit method in conjunction with Slide sub-objects. So basically the coordinates of an actually object aren't as important when calculating AOIs, just the object's name. This hit test just looks at where the eyes are on the screen and whether or not they are currently above any Slide sub-objects. I honestly do not know why your AOI shows nothing when the hit test suggests that the gazes are within the fixation or stimuli. The AOI isn't taking an average of anything it's literally just going "is the user looking at this sub-object?". This issue may be because of the script in your SaveGazeData InLine object. That is the first place I would look.
I hope this is helpful.
Devon Struthers