You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SendGazeReportUm(long X, long Y, unsigned long long timestamp);
SendGazeReportPixel(long X, long Y, unsigned long long timestamp);
The current SendGazeReportXX methods expect timestamp to be supplied by the user. In certain scenarios, the user may not have timestamps and should be able to use the API where the API itself calculates the timestamps internally.
The text was updated successfully, but these errors were encountered:
I am assuming that the timestamp is in milliseconds but it would be good to have a short description (or a more descriptive name) that tells whether it is relative or from epoch. E.g. timestamp_ms_from_epoch, timestamp_ms_relative etc.
Good point, clarity would definitely help in this case. in reality I believe under the covers it is mostly ignored as long as it is positive and increasing, but we should do the right thing.
SendGazeReportUm(long X, long Y, unsigned long long timestamp);
SendGazeReportPixel(long X, long Y, unsigned long long timestamp);
The current SendGazeReportXX methods expect timestamp to be supplied by the user. In certain scenarios, the user may not have timestamps and should be able to use the API where the API itself calculates the timestamps internally.
The text was updated successfully, but these errors were encountered: