Thanks Dardo, I wanna go through this in detail and I'll get back to you with some comments :).
Stefan, as I am working through this, I am wondering the following. What is the proper way to use the new co::CustomI/OCommand system to get this type of back-and-forth communication going between a render node (at whatever level, Window, Channel, Node, etc) and the main config? I've been going through EQ's source code and it seems that everything is handled by sending messages directly to the server node. i'm a bit fuzzy on how messages are routed past that point. How would I go about: a) Transmitting a custom command from the application node to all render nodes b) Transmitting a custom command from a single render node back to the application node For (b) it seems that through the config I can get a pointer to the application node through an experimental API (co::NodePtr getApplicationNode()). Is this safe to do so? Is the proper way to achieve (a) just sending the message to the Server? Thanks! -Harris -- View this message in context: http://software.1713.n2.nabble.com/Communicating-information-FROM-the-rendering-code-to-the-application-logic-tp7585385p7585415.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
