API specifications for a 2-way client/server solution

[Samour]

BTW, what do you mean by "blink position"?

Well corneal Reflex means blinking... which is why I was wondering why it had a position associated with it. So I guess it's supposed to say corneal reflection. No worries. Thanks for the info.

[martintall]

3. Information about pupil and corneal reflections cannot be accessed from the main GUI window right now (nor with the network client). I'll add the code to do so and to save it in another log file. Maybe Martin can make the modifications in the network client/server.

Sure thing, I've prepared the network client/server to broadcast more parameters than accessible through the first release. The StreamFormat class is intended to allow user configurable selection of the outgoing stream from the tracker. Ideally the tracker and client will operate on an identical GazeData structure so that the network transmission is transparent, raising OnGazeData event with a new object. People would then be free to subscribe to the tracker or the client as they wish, but over time a bunch of modifications to the core server is not ideal. Hence, the whole reason for the API..

Drop me an email when the tracker code has been modified and I'll have the client updated shortly.

Samour, I know that the start/stopping of the network services is a little bit buggy, the lame solution so far has been to check/uncheck the boxes.

I would recommend the WPF Toolkit as it's seen some development efforts, I'm currently using parts of it and it's working OK.

You are right about the TRACKER_STATUS not returning any values because it's not implemented yet! The STREAM_START should work is the socket is connected. In general the client/server implementation is to be considered work-in-progress, contributions are welcome.