-
Notifications
You must be signed in to change notification settings - Fork 27
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
Feature: Event system #18
Comments
We're still working on the extensions for interaction events. We've hit a couple of unanticipated issues, so unfortunately it will not be ready today. However, it should be complete this week. Apologies for the delay, and thanks for your patience. |
Thanks for the update. We're also still waiting for our touch module (they brought a 2x2...), so it's not super-urgent anyways. |
Will you be using TUIO to interact with the wall? Will you be interacting directly to the wall or through a tablet/phone? I just wanted to clarify your use scenario so we can properly target development. Right now we have TUIO supported around the idea of interaction via tablet, but not directly at the surface. How will you be using touch and will it be TUIO-based? |
We hope to use TUIO directly on the wall with our touch. Since we're still missing the touch, we don't know if it works out of the box. Mid-term we'll likely also install a Kinect. How would a tablet interaction look like? Is there an app? |
Great. For IOS there is TUIOPad, and for Android there is TUIODroid. They act as a multi-touch input device for your wall. This is the type of interaction currently supported with DisplayCluster. We will need to add some specific features to make TUIO interaction at the wall surface work as you expect. We'll work on that over the next couple of weeks using our smaller multi-touch wall. |
Quick update: we're still working on this, but having issues with our networking code that we've so far been unable to solve. Basic interaction is working--however until we solve the networking issue it's not reliable enough to commit. |
Need a separate event API where applications can subscribe and act on events processed by DC, e.g, be able to rotate/pan/zoom the model rendered. This is an expansion to the network interface that allows two-way communication of interaction events. For example, the remote application could manipulate the windows on DC, or interactions at the tiled display could be streamed back to the application and processed.
The text was updated successfully, but these errors were encountered: