Hi, On 4. Mar 2012, at 6:48, cpapado [via Software] wrote:
> What I want to facilitate is for the user on the application node to be able > to, using the mouse, pick points on an EQ window, then unproject them and ray > cast them for selecting objects. You should do that by using the RenderContext attached to the event. That said... > Back in 1.2.1, there used to be getCanvas()/getChannel() methods exposed > through the API as public (but I guess for internal use) which let me do what > I wanted, but these seem to be gone in 1.3.0. ...Not sure which functions you were using. Anything marked with '@version x.y' is public API and should not be removed. You should still be able the get from config to all canvases, segments, layouts, views and observers. Furthermore you can get from your channel to window, pipe and view. Anything else is potentially dangerous (racy) and you'll need to present a use case for why you need this. > I would use those to convert the x,y coordinates of the mouse click event to > viewport coordinates for the channel then proceed to unproject using the > frustum for the canvas that the channel was rendering (that was a convention > on my configuration). All that information should be in the render context attached to your event. If you get it through other means (except Window::getRenderContext) will give you wrong information in some cases. HTH, Stefan. -- View this message in context: http://software.1713.n2.nabble.com/Suggested-way-to-pull-canvas-wall-geometry-from-inside-eq-Config-tp7341673p7345590.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
