I’ve been playing with stereo support in ParaView for sometime now and here are some ideas to improve the UX. I wanted to get a feel for what people think.
- ParaView Qt client will always attempt to create an active-stereo-capable context. If not supported on system, then the Crystal Eyes stereo mode will not be shown in the UI. This enables/implies the following:
paraview --stereowill no longer be needed or supported.
ii. Stereo rendering can be enabled/disabled by simply clicking on a toolbar button. The button can show a drop-down menu to enable choosing the stereo type e.g. anaglyph, red/blue, etc. This button may only affect the active view or all views. It seems reasonable to me to affect all views since if you’re wearing stereo glasses, I’d expect you’d be wearing them when looking at any of the views and not just the active one – but we could go either way.
paraview --stereo-type=[type]is same as using the toolbar button to change stereo mode except via command line.
iv. Changing stereo mode using the tool button will only affect the Qt application. It won’t get saved in state files etc.
pvbatchwill continue to support
--stereo-type=[type]arguments which will act as standin for the toolbar button shown in the Qt client for the same effect. Note, here too,
--stereoargument is no longer necessary or supported.
--stereo-type=[type], however it will only be relevant and used in cases where the server displays results to the user i.e. tile-display mode and CAVE mode. For conventional client-server mode were the final rendering results are shown in the Qt client (or pvpython), the server processes don’t need this argument since the client will drive the stereo mode.