(Kyle, I think you're probably the one to answer this.)
I've posted the question a couple times before, but haven't gotten a response.
I have a bit more information now.
I have a modal ViewController ("Details") that I present with custom
presentation and animations (the presented VC is smaller than the screen, and
there is chrome that dims the background). While that's up, a second modal VC
("Viewer") can be presented, this one is currently using the default
presentation. This all works fine.
When the second VC is dismissed, the original VC is sent viewWillAppear(). Then
its frame is changed to be the full size of the screen (several times), then it
appears, then viewDidAppear() is called, then the custom presentation
sizeForChildContentContainer(…) is called, and then the presented VC is resized
to its correct, smaller size.
In that stage between the second VC being dismissed and the first VC being
re-shown, its size is changed without consulting
sizeForChildContentContainer(…). This seems like a bug. But is there any way to
work around it?
Side note: it seems that the distinction between presenting a view (modal), or
pushing a view (nav controller), or showing a tab (tab controller) are rather
artificial, and could be combined into a single conceptual code path, with only
the visual style differentiating them. That would make it a lot easier to
re-use custom transitions/presentations in different situations (e.g. via
segue, or programmatic presentation, or push, etc.)
Thanks!
--
Rick Mann
rm...@latencyzero.com
_______________________________________________
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
