<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Two awkward things about iPhone development</title>
	<atom:link href="http://www.gogo-robot.com/2009/06/07/two-awkward-things-about-iphone-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gogo-robot.com/2009/06/07/two-awkward-things-about-iphone-development/</link>
	<description>Independent Games Developer</description>
	<lastBuildDate>Sun, 18 Jul 2010 20:35:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: E Beland</title>
		<link>http://www.gogo-robot.com/2009/06/07/two-awkward-things-about-iphone-development/comment-page-1/#comment-30</link>
		<dc:creator>E Beland</dc:creator>
		<pubDate>Mon, 19 Apr 2010 12:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.gogo-robot.com/?p=69#comment-30</guid>
		<description>Thanks for the post I was about to write a whole ton of code to solve a modal to modal transition problem...</description>
		<content:encoded><![CDATA[<p>Thanks for the post I was about to write a whole ton of code to solve a modal to modal transition problem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rew</title>
		<link>http://www.gogo-robot.com/2009/06/07/two-awkward-things-about-iphone-development/comment-page-1/#comment-24</link>
		<dc:creator>Rew</dc:creator>
		<pubDate>Wed, 31 Mar 2010 19:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.gogo-robot.com/?p=69#comment-24</guid>
		<description>Thanks! As you say, it is a long time since the post was put up, and Apple may have change things internally / fixed bugs that were there since then, so certain things in there may or may not be relevant :)</description>
		<content:encoded><![CDATA[<p>Thanks! As you say, it is a long time since the post was put up, and Apple may have change things internally / fixed bugs that were there since then, so certain things in there may or may not be relevant <img src='http://www.gogo-robot.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dev Kanchen</title>
		<link>http://www.gogo-robot.com/2009/06/07/two-awkward-things-about-iphone-development/comment-page-1/#comment-23</link>
		<dc:creator>Dev Kanchen</dc:creator>
		<pubDate>Wed, 31 Mar 2010 19:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.gogo-robot.com/?p=69#comment-23</guid>
		<description>Great post! I am reasonably comfortable with UIKit but looking at low-level stuff like custom drawing routines makes me nervous. :)

Long time since this post was originally put up, but I will chip with some of my thoughts anyway:

&quot;....I’m guessing it’s because the modal view controller for the parent view controller is still pointing to the one that’s just disappeared, and that this gets cleaned up after viewDidDisappear is called, so any new modal view controller you set in viewDidDisappear is reset straight after the function returns (because the parent view controller is still in the process of cleaning up the first one)...&quot;

Not sure if that is entirely true. I have called &#039;presentModalViewController&quot; on the parent even BEFORE viewDidDisappear and that has worked. With one modal sliding in and another sliding out at the same time, it didn&#039;t look pretty. But it worked.

One reason why the call from viewDidDisappear of the first modal might not have worked could be that the view is released as soon as it disappears. Posing a counter-point to myself, I would imagine that the API would call viewDidDisappear before removing the modal from the window and then releasing it. But the only way to confirm/reject either theory would be to check with some NSLogs in viewWill and viewDidDisappear.</description>
		<content:encoded><![CDATA[<p>Great post! I am reasonably comfortable with UIKit but looking at low-level stuff like custom drawing routines makes me nervous. <img src='http://www.gogo-robot.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Long time since this post was originally put up, but I will chip with some of my thoughts anyway:</p>
<p>&#8220;&#8230;.I’m guessing it’s because the modal view controller for the parent view controller is still pointing to the one that’s just disappeared, and that this gets cleaned up after viewDidDisappear is called, so any new modal view controller you set in viewDidDisappear is reset straight after the function returns (because the parent view controller is still in the process of cleaning up the first one)&#8230;&#8221;</p>
<p>Not sure if that is entirely true. I have called &#8216;presentModalViewController&#8221; on the parent even BEFORE viewDidDisappear and that has worked. With one modal sliding in and another sliding out at the same time, it didn&#8217;t look pretty. But it worked.</p>
<p>One reason why the call from viewDidDisappear of the first modal might not have worked could be that the view is released as soon as it disappears. Posing a counter-point to myself, I would imagine that the API would call viewDidDisappear before removing the modal from the window and then releasing it. But the only way to confirm/reject either theory would be to check with some NSLogs in viewWill and viewDidDisappear.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
