To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=60699
User thb changed the following:
What |Old value |New value
================================================================================
Status|STARTED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jan 25 07:20:47 -0800
2006 -------
Here, X11 sal's YieldGraphicsExpose() seems to be the primary culprit
Function first introduced in salgdi2.cxx:1.21, with vcl7pp1r3.
The fix was done for SO7, corresponding issue is issue 20249. The original
code in SO7 is:
void SalFrameData::YieldGraphicsExpose()
{
XEvent aEvent;
do
{
while( XCheckTypedWindowEvent( GetXDisplay(), GetWindow(), Expose,
&aEvent ) )
HandleExposeEvent( &aEvent );
XIfEvent( GetXDisplay(), &aEvent, GraphicsExposePredicate,
(XPointer)this );
if( aEvent.type == NoExpose )
return;
HandleExposeEvent( &aEvent );
} while( aEvent.xgraphicsexpose.count != 0 );
}
which is _only_ called from SalGraphics::CopyBits() (i.e. this fixes
_only_ the described bug, nothing else).
For OOo2.0, now all places that could possibly generate GraphicsExpose events
(which are by default enabled for (nearly) all GCs) now call
YieldGraphicsExpose(), which now also contains two nested polls, in case the
guaranteed GraphicsExpose or NoExpose events don't show up in time. Now, this
a) relies on round-trip times to be _always_ less than two seconds
b) introduces full round-trips for _every_ pixmap/blit operation
c) syncs every animation to server/network/socket timing (plus the kernel
scheduler), which is what this bug is all about.
Fixed by at least reducing the YieldGraphicsExposure() call to the single
necessary case (i.e. blitting within a single window). More elaborate solution
scheduled for OOo 3.0 (async GraphicsExposure handling)
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]