<rdar://problems/3566400> GL_APPLE_flush_render problems *
<rdar://problems/3566403> GL_APPLE_flush_render enhancement **
<rdar://problems/4075545> 10.4.1 (8B9) general performance - sluggish
<rdar://problems/4103784> 10.3 (7W98) - QT 7.0 poor CoreVideo
performance
<rdar://problems/4110581> OpenGL glFlush/glFlushRenderAPPLE take
5x longer on Tiger
<rdar://problems/4113808> QuartzCore.framework can't be
weak_linked, 10.3.9 SDK incompatibility
<rdar://problems/4119986> 10.4.1 (8B15) - Quartz CGS enforces auto-
beam-sync for ALL app's
Thanks for the radars. I'll have a look when I get a chance.
As it is, the blocking behavior is enforced for all apps (which
might be another bug, since it's only supposed to affect
executables linked against Tiger, correct?), but the way it blocks
is wrong, IMO.
Pre-Tiger and CFM applications do not initiate the beam sync
behavior. But if you have another Tiger Mach-O application flushing
in the same vbl, then all updates will be coalesced for that vbl.
That's what you are seeing. That's by design. You can argue, and you
have been, that this is wrong, but this is the current Tiger
implementation. We should have more info at WWDC and can discuss
further in the labs.
haroon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/email@hidden
