Hi Stephan,
On 18 October 2013 14:38, Stephan Maximilian Huber < [email protected]> wrote: > I refactored the code so it uses the WindowingSystemInterface to get/set > the menubar-behavior. I am a bit unsure when to set the behavior from the > DisplaySettings-object, as the WindowingSystemInterface is created on > demand. See the attached code. > Thanks, just done a first pass review, will do another soon once I've got some feedback from you and done some thinking myself. One thought occurred to me is that we could have another MenubarBehavior that says do nothing - just leave the setting as is. I'm thinking this would probably be the default, then we can have the existing behaviour, that we then override when required. > It'd be nice to have a mechanism to pass some application- / > platform-specific parameters to the WindowingSystemInterface when it gets > created. > The WindowSystemInterface gets constructed by a proxy object or via a static method for registering it, in both cases this will be one of the first things the application does on start up. Given this provide application specific settings is not practical. What you should be able to do is in the main, or viewer construction/realize() is get the WindowSystemInterface and explicitly set the values required. While I haven't yet thought through the topic enough, I do wonder if realize() method might be the place to do it as this will have the DisplaySettings object available and can be done before/after the window creation. I can potentially make some of the changes once we agree a way forward. Thoughts? Robert.
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
