On Mon, 2008-10-06 at 09:15 +0100, Robert Osfield wrote: > Hi J-S, > > > OK, I'll do it Monday morning and resubmit. I'd make it as wide as the bar > > Thanks. > > Wr.t. osgWidget based stats, this would make a lot of sense, one would > have to resolve the dependency between osgViewer and osgWidget as > right now osgWidget depends upon osgViewer, but this should be doable.
The WindowManager class only depends on osgViewer because it needs a View object to call computeIntersections on. If I could pick some other way (perhaps by just copy/pasting the code from osgViewer::View?), this dependency wouldn't exist. > Robert. > > On Sat, Oct 4, 2008 at 4:01 PM, Jean-Sébastien Guay > <[EMAIL PROTECTED]> wrote: > > Hi Robert, > > > >> Putting the graph below the existing bar graph would help. > > > > graph (= as wide as the main view), but what height would make sense? Too > > small a height and small variations will not be visible, but too big a > > height will take too much space... A default of maybe 100 or 200 pixels, > > would that sound about right? > > > > It doesn't help that the available vertical space depends on the number of > > cameras/views... So if you have lots of views, the new stats that were added > > lately (number of each node type, vertices, etc.) will not be visible. > > That's why I was trying to save vertical space by putting the graph in the > > same space as the bar graph. > > > > It would be cool to have something like NVPerfHUD, where each part of the > > stats HUD they have is a window which you can drag around, minimize (window > > shade style - the window collapses into just its title bar) or close. That's > > kind of the ultimate in customizability, and when the windows are not fixed, > > you worry less about screen space. Perhaps osgWidget could be leveraged to > > implement something like this into the StatsHandler, now that it's available > > out of the box in OSG? :-) > > > >> Longer term it'd be nice to have the control to decide where you want > >> the graphs (screen as well as position) and their size. Such as > >> generalization could support having Camera stats and View stats > >> overlaying the viewport they are associated with. > > > > Definitely. Right now the StatsHandler is a really opaque class that does > > everything in a hard-coded way, which is something I'd like to work on > > sometime (as you may have seen in my other message to Roland). > > > > Anyways, baby steps :-) > > > > J-S > > -- > > ______________________________________________________ > > Jean-Sebastien Guay [EMAIL PROTECTED] > > http://www.cm-labs.com/ > > http://whitestar02.webhop.org/ > > _______________________________________________ > > osg-submissions mailing list > > [email protected] > > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
