Hi, On Thu, 2010-06-10 at 14:34 -0500, Carsten Neumann wrote: > Hello Johannes, > > Johannes Brunen wrote: > > might it be possible that the PassiveWindow::terminate() function does > > need to call Inherited::doTerminate() ??? > > > > However, currently I'm not sure about this... > > hm, honestly I'm not sure either, the Window::something > Window::doSomething thing is a bit confusing to me. > > I understand that some of it comes from the requirements of the parallel > drawer being able to activate the OpenGL context when needed, but with > both Window::something and Window::doSomething being virtual I'm not > certain which functions are meant to be overridden by derived classes > and if BarWindow::something should call Window::something internally or > rather Window::doSomething... > > Gerrit, can you give me a hint what the idea behind each set of > functions is (was? ;) )?
usually it was doSomething does the work and something is there to delegate it. The uncertainty comes in because I never really solved it correctly for the passive window yet. This one might actually have to override both, glut/qt windows might be similar as they mess with the context behind OpenSGs back too. As I'm looking into it just now because of the gl id problems and par multi win drawer crashes give me a second to look at the passive window again In general I tend to agree with Carsten to make the terminate function pure virtual inside the window class. Let me just try where this takes us. kind regards gerrit ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
