Comments on: Fix for Troublesome User Interface (UI) Updates http://iPhoneDeveloperTips.com/user-interface/fix-for-troublesome-user-interface-ui-updates.html iOS Developer Tips, Tricks and Tutorials. Wed, 08 Feb 2012 06:31:16 -0600 hourly 1 http://wordpress.org/?v=3.3.1 By: Imthiaz http://iPhoneDeveloperTips.com/user-interface/fix-for-troublesome-user-interface-ui-updates.html#comment-5401 Imthiaz Fri, 02 Oct 2009 07:37:27 +0000 http://iPhoneDeveloperTips.com/?p=2823#comment-5401 Hi John Can you use performSelector when you are in the main thread. I use it a lot when I am using procedures using NSInvocationOperation. Another tip which I would like to give. You can have a Default.png in your application and that will get loaded 1st when you start your application. This will avoid your screen looking black. Thanks Imthiaz Hi John

Can you use performSelector when you are in the main thread. I use it a lot when I am using procedures using NSInvocationOperation.

Another tip which I would like to give. You can have a Default.png in your application and that will get loaded 1st when you start your application. This will avoid your screen looking black.

Thanks
Imthiaz

]]> By: Didier Prophete http://iPhoneDeveloperTips.com/user-interface/fix-for-troublesome-user-interface-ui-updates.html#comment-5400 Didier Prophete Fri, 02 Oct 2009 05:24:59 +0000 http://iPhoneDeveloperTips.com/?p=2823#comment-5400 > I’ve found that a few performSelector calls sprinkled about judiciously > can work wonders for a UI that isn’t cooperating. I couldn't agree more. I have run into similar problems and this saved my life over and over again. Also, note that using an afterDelay of 0 will simply execute the code once the next UI event loop starts (very similar to using callLater() in Adobe Flex/AIR) > I’ve found that a few performSelector calls sprinkled about judiciously
> can work wonders for a UI that isn’t cooperating.

I couldn’t agree more. I have run into similar problems and this saved my life over and over again. Also, note that using an afterDelay of 0 will simply execute the code once the next UI event loop starts (very similar to using callLater() in Adobe Flex/AIR)

]]>