(Just noticed that I posted this on quartz-dev, not here. [Didn't get
an answer to my question there, either, natch.] For the archives,
here's a very questionable workaround to the problem I was having..)
On Jul 18, 2008, at 11:52 AM, Dave Hayden wrote:
Just wanted to see if this is expected behavior, and if there's a
workaround. When I add or remove one sublayer and change another's
position in the same transaction, the moved layer leaves a "ghost"
image that fades away at the start position. If I wrap the two
actions in CATransaction begin/commit, it works as expected (no
ghost image) if I do the position change first, then the add/remove.
If I do the add/remove first, I get the ghost image.
Found a workaround, and it's an ugly one: If I call
[[NSRunLoop currentRunLoop] runMode:NSDefaultRunLoopMode
beforeDate:nil];
between the actions they won't interfere with each other. Ick.
Any idea how safe this is? <cue chirping crickets>
-D
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
