Issue 6: GameCanvas.flushGraphics not implemented correctly
Status:  Fixed
Owner:
Closed:  Jan 2010
Project Member Reported by bar...@gmail.com, Nov 18, 2009
Now, in MicroEmulator, a call to flushGraphics results in a call to
repaint, which is not correct.

This causes many applications (esp. games) to flicker badly.

A call to flushGraphics should put the (already drawn) backbuffer on
screen.
Or, as SonyEricsson describes it:
"A call to flushGraphics() is similar to calling repaint(); and
serviceRepaints(); in sequence, but the difference is that flushGraphics()
does not generate a call to your paint() method."
Jan 6, 2010
Project Member #1 bar...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Jan 17, 2010
Project Member #2 bar...@gmail.com
Fixed in trunk (future 3.0 version)
Status: Fixed
Labels: Milestone-3.0