Unable to set screen values via socket

All development related discussions that does not concern a specific programming language. For example, JSON data format, server communication etc.

Unable to set screen values via socket

Postby Rafael » 03 Mar 2014, 07:24

Hi,

Sorry if I'm posting on the wrong section. Although I'm using C++, the problem doesn't seem to be linked to the language directly (as a suggestion, I think there should be a "general" forum under "Development" for questions regarding EyeTribe API, JSON messages, and so on)

Anyway, I was trying to connect to the eyetracker via socket and send JSON messages. So far I'm able to do basic comunication (such as enabling push mode, receive eye position, etc). But when I try to set screen values (resolution and physical dimensions), the server returns this message:

Code: Select all
{"category":"tracker","request":"set","statuscode":400,"values":{"statusmessage":"All screen values must be set at the same time"}}


This is the string I'm sending:

Code: Select all
{"category":"tracker","request":"set","values":{"screenindex":0,"screenresw":1920,"screenresh":1080,"screenpsyw":0.51,"screenpsyh":0.29}}


Can anyone shed some light on this, please? Thanks in advance.

Regards,

Rafael
Rafael
 
Posts: 13
Joined: 20 Feb 2014, 23:33

Re: Unable to set screen values via socket

Postby Martin » 03 Mar 2014, 17:21

Hi Rafael,

There was a bug with the handling of screen physical size, it has been resolved and the fix is scheduled for inclusion with next release. Sorry for the inconvenience.
Martin
 
Posts: 567
Joined: 29 Oct 2013, 15:20

Re: Unable to set screen values via socket

Postby Rafael » 03 Mar 2014, 18:12

Ok Martin, thanks again.

Is there a public bug repository for the project? Since [currently] EyeTribe is mostly used by developers, It would be nice to have access to the list of known bugs, and we could also submit bug reports.
Rafael
 
Posts: 13
Joined: 20 Feb 2014, 23:33

Re: Unable to set screen values via socket

Postby Martin » 04 Mar 2014, 00:48

Right now we don't have a public ticketing system but we use one internally to keep track of all bug reports and feature requests. Release schedule is every two weeks given that there are significant improvements to stability or performance.
Martin
 
Posts: 567
Joined: 29 Oct 2013, 15:20


Return to General