> >>In general, adding flush() calls is not the correct way to fix bugs > >>(and can impact performance). This flush is probably hiding the true > >>cause of the bug. Unfortunately, I don't know what that would be. > >> > > I don't know exactly the reason. > It seems that some rendering is delayed to the next frame. > So I add flush here to make them visible in the current frame. >
Is this still being tracked down? we should probably revert the hack if nobody is actually going to look for the proper fix. Dave. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
