Re: [eq-dev] Tracking Input
Stefan Eilemann
On 26. Jan 2012, at 19:25, oliver [via Software] wrote:
> I am very new to Equalizer and have a question:
Welcome!
> I want to add a TUIO tracking client to an Equalizer based application (1 node, multiple GPUs). What would be the best entry point?
What do you want to track?
1) The head of an observer? Use Observer::setHeadMatrix, see eqPly and Programming Guide for details
2) Some scene objects? This is application logic, and I suggest that you do the proper scene updates after Config::finishFrame.
HTH,
Stefan.
--
View this message in context: http://software.1713.n2.nabble.com/Tracking-Input-tp7227755p7229427.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.
_______________________________________________
eq-dev mailing list
eq-...@equalizergraphics.com
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com
Stefan Eilemann
On 27. Jan 2012, at 11:26, oliver [via Software] wrote:
> I am evaluating equalizer to use with a multitouch display wall. So there are several touch cursors with position parameters.
> Your proposal using Config (and perhaps frameData to share the data between nodes) looks perfect.
> As I understand until now I don't have to differentiate between "master" and "slave" in the config, because the config is only initialized on the app node?
The application calls Config::init only on the appNode. On render clients, Client::initLocal does not return.
The model of having all the event handling logic in the application is typically the most simple and robust. One can however also implement a distributed event processing and data handling, with all the complexities that entails.
HTH,
Stefan.
--
View this message in context: http://software.1713.n2.nabble.com/Tracking-Input-tp7227755p7230278.html