Comments on: Two awkward things about iPhone development

By: Tom

Tom — Tue, 19 Oct 2010 14:04:22 +0000

Cheers mate!!! (had a look at it once and didnt get it to work for some reason.. but you made me looking at it again and I found what I was previously missing..)
Thank you heaps!

keep on the good work!
peace
Tom

By: Rew

Rew — Mon, 18 Oct 2010 14:46:51 +0000

Hi Tom. What iOS version are you tagetting? If it's 3.2 and above, Apple now allows you to load custom fonts without all the hassle of doing it manually. Take a look at the UIAppFonts key in the application's plist file: http://developer.apple.com/library/mac/#documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html

By: Tom

Tom — Mon, 18 Oct 2010 14:39:50 +0000

Hi,

thanks for this nice example. but I have trouble reading Cstrings with a Umlaut and converting them into char / glyphs.
I tried all sorts of encodings but I didnt get it to work. do you have any hints for me?
cheers

Tom

By: E Beland

E Beland — Mon, 19 Apr 2010 12:36:13 +0000

Thanks for the post I was about to write a whole ton of code to solve a modal to modal transition problem…

By: Rew

Rew — Wed, 31 Mar 2010 19:19:05 +0000

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

By: Dev Kanchen

Dev Kanchen — Wed, 31 Mar 2010 19:14:40 +0000

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:

“….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)…”

Not sure if that is entirely true. I have called ‘presentModalViewController” 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’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.