Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add frame sequence number to refresh callback inside TuioDispatcher #17

Closed
wants to merge 9 commits into from

Conversation

kryptokommunist
Copy link

How about exposing the frame sequence number in the TuioListener.refresh callback?

@tweigel-dev
Copy link
Owner

Hay,
Thanks for your PR and sorry for my late response!
Nice that someone else want to do something with the TUIO Protocoll in Python ;)
The whole feathre reagring TUIO Time is not implemented here.
Do you think that your suggestion is the right behavior?
I get the refresh function form the c++ documentation as following
Detailed Description
http://www.tuio.org/?cpp

The TuioTime class is a simple structure that is used to reprent the time that has elapsed since the session start. The time is internally represented as seconds and fractions of microseconds which should be more than sufficient for gesture related timing requirements. Therefore at the beginning of a typical TUIO session the static method initSession() will set the reference time for the session. Another important static method getSessionTime will return a TuioTime object representing the time elapsed since the session start. The class also provides various addtional convience method, which allow some simple time arithmetics.

AND
image
that means that we have to store a time relative to the start of a session. therefore we have to hold the current time. Maybe with a incrementing time thread or with the local os time.

@kryptokommunist
Copy link
Author

Hey there, no worries. I take my time as well :)

I am using Tuio for a software that is "abusing" the protocol to send location data of a laser tracking system by this guy. In that context exposing the frame sequence number made sense to me. But if that is not in the protocol this shouldn't be merged I guess. Then it's just a hack using the protocol not as intended.

@tweigel-dev
Copy link
Owner

Is this PR still requested?

@kryptokommunist
Copy link
Author

No thanks, all good :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants