Hi, I have found a little difference between 1.8 and 2.0 which is problematic. I'm using PassiveWindow and have implemented a custom scene manager which basically calls the PassiveWindow 'render' method. Now, this one is not implemented in PassiveWindow and the base implementation of Window is called. This one however calls 'doSwap' (note that this is different from 1.8 where simply the 'swap' method was called), which is also not implemented in PassiveWindow. Therefore the base Win32Window implementation is called which does directly call system SwapBuffers. This call howerver is assumed to be performed by the host application in my setup.
Either the PassiveWindow must have a basically emtpy 'doSwap' implementation or the Window render method has to call 'swap' instead of 'doSwap'. IMHO the latter one is the correct choice. What is the reason for the introduction of the 'doSwap' indirection? Alternatively, I could implement the 'render' call myself, but I think that the above is a flaw and should be corrected. I did found message http://www.mail-archive.com/[email protected]/msg11580. html but with little help. I have checked rev 2039 and found the same code as in my setup. Best regards, Johannes ____________ Virus checked by G DATA AntiVirusKit Version: AVF 19.498 from 13.08.2009 Virus news: www.antiviruslab.com ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
