On Wednesday 24 October 2012 17:01:37 Aashish Chaudhary wrote: > The way it works now is that you create a connection manager (lines > 475 - 483), which will be generated by the GUI if used, and then for > the styles, > you would link it with the ID of the proxy and its specific property > that you want to control. Now said that the GUI shows you the name of > the proxy and not the ID > for obvious reasons. Then depending upon the type of the proxy and > property you specify a particular input from a HCI device. Currently > we support analog, button, and tracker. > > The wiki here is bit old: > http://www.paraview.org/Wiki/ParaView/Users_Guide/CAVE_Display
Yes, I noticed. Together with the information in a thread on this list (http://www.paraview.org/pipermail/paraview/2012-July/025507.html), it was quite valuable, though... > We wrote a source article as well: > http://www.kitware.com/source/home/post/66 Thanks, I didn't see that before. > > This recent work is not in master yet (hopefully this Friday) but you > can checkout this branch: vtk_vr_improvements_new_gui > if you want to from paraview stage repository. The branch contains > bunch of bug fixes, and API improvements. That's great news -- I wasn't aware that the GUI work is this close to entering master. The screenshot looks promising. I will definitely try it out next week. Thanks, Johannes _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview