Am 14.09.2009 um 18:32 schrieb Matt Neuburg:
Ah, but the crux of my question is that I don't have "the next one
to show".
I don't know what the window will look like when selecting a
different core
data entity until I select it, and by then it's too late. That's why
I'm
asking for a strategy...
Have you tried creating an NSTabView, containing the same views on
two different pages? There's sample code that does the effects to
transition between two tabs.
Now you may think: "I already told him I didn't have the second
page.", but play along for a moment. If you can manage to load the new
values only into the tab that isn't currently current, you'll have one
view with the old image, and one with the new one. Then do the page
curl and the new data will appear just as you like.
This is less scary than your window-based code, and could even be
put into a generic, re-usable controller class that creates the tab
view around your items and duplicates them on two tabs, and its
accessors could change the currently visible view when you're not in a
context where you want to animate.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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 arch...@mail-archive.com
