Home › Forums › Software Development › Developing Software for I-Series
- This topic has 1 reply, 2 voices, and was last updated 6 years ago by Grant [Tobii].
- 21/03/2017 at 16:22 #6544Kevin BraswellParticipant
I am developing a standlone .NET app for the I-Series device. At one point, I did a proof of concept app that ran using gaze SDK on the i-Series (Not using Windows Control). This was a successful test, however I did not run Communicator simultaneously.
I need someone to confirm the following before we build our next release:
1. Is Gaze SDK the correct sdk to leverage in this use case? Or EyeX?
2. Can our stand alone app use the global eye tracking settings/configuration (dwell/click -right-left eye – calibration, etc) if they have already been set?
3. Will our standalone app running at the same time Communicator is running cause any potential issues or system resource conflicts?
4. Does the I-Series device use the EyeX engine?
We are NOT using Windows control.
Here is our environment:
Windows 10 – Eye Series I-12
Our App is a standalone .NET
Please email me at [email protected] or call @ (205) 868-9311 with any questions.22/03/2017 at 19:56 #6559Grant [Tobii]Keymaster
Hi Kevin, I replied already to this post on a seperate thread and sent you a personal email with instructions on who to contact at Tobii about this.
- You must be logged in to reply to this topic.