<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iphone on Arcanelab Blog</title><link>https://blog.arcanelab.com/tags/iphone/</link><description>Recent content in Iphone on Arcanelab Blog</description><generator>Hugo</generator><language>en-US</language><copyright>Zoltán Majoros</copyright><lastBuildDate>Tue, 20 Dec 2011 19:03:00 +0100</lastBuildDate><atom:link href="https://blog.arcanelab.com/tags/iphone/index.xml" rel="self" type="application/rss+xml"/><item><title>iPhone OpenGL Speed Tip – Turn Off Thumb Instructions</title><link>https://blog.arcanelab.com/2011/12/iphone-opengl-speed-tip-turn-off-thumb-instructions/</link><pubDate>Tue, 20 Dec 2011 19:03:00 +0100</pubDate><guid>https://blog.arcanelab.com/2011/12/iphone-opengl-speed-tip-turn-off-thumb-instructions/</guid><description/></item><item><title>Getting the UDID of an iOS device [[UIDevice currentDevice] uniqueIdentifier]</title><link>https://blog.arcanelab.com/2011/01/getting-the-udid-of-an-ios-device-uidevice-currentdevice/</link><pubDate>Tue, 18 Jan 2011 19:48:00 +0100</pubDate><guid>https://blog.arcanelab.com/2011/01/getting-the-udid-of-an-ios-device-uidevice-currentdevice/</guid><description>&lt;h1&gt;Getting the UDID of an iOS device&lt;/h1&gt;
&lt;pre&gt;[[UIDevice currentDevice] uniqueIdentifier]&lt;/pre&gt;</description></item><item><title>Enabling C++ constructor calling from Objective C</title><link>https://blog.arcanelab.com/2010/11/enabling-c-constructor-calling-from-objective-c/</link><pubDate>Mon, 01 Nov 2010 20:51:00 +0100</pubDate><guid>https://blog.arcanelab.com/2010/11/enabling-c-constructor-calling-from-objective-c/</guid><description/></item><item><title>MBProgressHUD</title><link>https://blog.arcanelab.com/2010/11/mbprogresshud/</link><pubDate>Mon, 01 Nov 2010 00:09:00 +0100</pubDate><guid>https://blog.arcanelab.com/2010/11/mbprogresshud/</guid><description/></item><item><title>how to debug EXC_BAD_ACCESS on iPhone</title><link>https://blog.arcanelab.com/2010/10/how-to-debug-exc-bad-access-on-iphone/</link><pubDate>Sat, 09 Oct 2010 13:57:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/10/how-to-debug-exc-bad-access-on-iphone/</guid><description/></item><item><title>Great guide for memory-debugging in Instruments</title><link>https://blog.arcanelab.com/2010/09/great-guide-for-memory-debugging-in-instruments/</link><pubDate>Thu, 30 Sep 2010 23:34:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/great-guide-for-memory-debugging-in-instruments/</guid><description/></item><item><title>Cocoa Dev Central's "Learn Objective C"</title><link>https://blog.arcanelab.com/2010/09/cocoa-dev-central-s-learn-objective-c/</link><pubDate>Sun, 26 Sep 2010 22:16:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/cocoa-dev-central-s-learn-objective-c/</guid><description/></item><item><title>A nice article on iPhone application internationalization</title><link>https://blog.arcanelab.com/2010/09/a-nice-article-on-iphone-application-internationalization/</link><pubDate>Sun, 26 Sep 2010 22:11:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/a-nice-article-on-iphone-application-internationalization/</guid><description/></item><item><title>Getting filepath to the Documents folder on iPhone To achieve the task written in the…</title><link>https://blog.arcanelab.com/2010/09/getting-filepath-to-the-documents-folder-on-iphone-to/</link><pubDate>Fri, 24 Sep 2010 18:07:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/getting-filepath-to-the-documents-folder-on-iphone-to/</guid><description>&lt;h1&gt;Getting filepath to the Documents folder on iPhone&lt;/h1&gt;
&lt;p&gt;To achieve the task written in the title of this post, you have to do the following:&lt;/p&gt;
&lt;pre&gt;NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES); 
NSString *documentsPath = [paths objectAtIndex:0];&lt;/pre&gt;</description></item><item><title>A fantastic collection of Xcode tips &amp; tricks</title><link>https://blog.arcanelab.com/2010/09/a-fantastic-collection-of-xcode-tips-tricks/</link><pubDate>Tue, 14 Sep 2010 01:07:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/a-fantastic-collection-of-xcode-tips-tricks/</guid><description/></item><item><title>Button resize causing text blur?</title><link>https://blog.arcanelab.com/2010/09/button-resize-causing-text-blur/</link><pubDate>Tue, 14 Sep 2010 00:44:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/button-resize-causing-text-blur/</guid><description>&lt;h1&gt;Button resize causing text blur?&lt;/h1&gt;
&lt;p&gt;Today I noticed a very, very strange behaviour (bug?) in Xcode. I am creating buttons for my iPhone application with a custom image background and a text on top of it. The Interface Builder attributes window looks like this:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Usually I change the font-family and size for my text, but when I do this, the button dimensions suddenly grow pretty big. So I just head over to the &lt;em&gt;Button Size&lt;/em&gt; tab and reset the dimension values to the originals, like so:&lt;/p&gt;</description></item><item><title>View overlapped by the title bar During the development of my latest iPhone project I…</title><link>https://blog.arcanelab.com/2010/09/view-overlapped-by-the-title-bar-during-the-development-of/</link><pubDate>Fri, 10 Sep 2010 20:04:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/09/view-overlapped-by-the-title-bar-during-the-development-of/</guid><description>&lt;h1&gt;View overlapped by the title bar&lt;/h1&gt;
&lt;p&gt;During the development of my latest iPhone project I faced a strange phenomenon: if I enable the title bar on a screen, the current view is placed to the coordinates (0,0), right beneath the title bar. Also, since the height of the view is not 100% (to leave space for the title bar), there&amp;rsquo;s an empty space left under the view.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s an example:&lt;/p&gt;</description></item><item><title>A very simple way to load a webpage with Cocoa NSError *error = [[NSError alloc]…</title><link>https://blog.arcanelab.com/2010/07/a-very-simple-way-to-load-a-webpage-with-cocoa-nserror/</link><pubDate>Thu, 22 Jul 2010 22:44:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/07/a-very-simple-way-to-load-a-webpage-with-cocoa-nserror/</guid><description>&lt;h1&gt;A very simple way to load a webpage with Cocoa&lt;/h1&gt;
&lt;pre&gt;&lt;p&gt;NSError *error = [[NSError alloc] init];&lt;br/&gt;NSURL *url = [NSURL URLWithString:@"http://www.google.com/"];&lt;br/&gt;NSString *content = [NSString stringWithContentsOfURL:url encoding:NSUTF8StringEncoding error:&amp;amp;error];&lt;br/&gt;&lt;br/&gt;&lt;/p&gt;
&lt;/pre&gt;</description></item><item><title>Clean &amp; rebuild Oh, boy.</title><link>https://blog.arcanelab.com/2010/07/clean-rebuild-oh-boy/</link><pubDate>Thu, 08 Jul 2010 01:37:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/07/clean-rebuild-oh-boy/</guid><description>&lt;h1&gt;Clean &amp; rebuild&lt;/h1&gt;
&lt;p&gt;Oh, boy. I&amp;rsquo;d been struggling with this for a while. I loaded a view from a nib, and my app kept crashing with an exception saying: &lt;em&gt;loaded the &amp;ldquo;foo&amp;rdquo; nib but the view outlet was not set&lt;/em&gt;. I was like WTH, I definitely connected the view outlet to the ViewController, what&amp;rsquo;s going on? I kept resaving the nib, recompiling the app, but to no avail.&lt;/p&gt;
&lt;p&gt;After digging some forum threads about this exception I got the idea of cleaning my builds. I did so, and guess what: after rebuilding my app it worked!&lt;/p&gt;</description></item><item><title>NSTimer invalidate When you create an NSTimer, and specify it to be a non-repeat…</title><link>https://blog.arcanelab.com/2010/07/nstimer-invalidate-when-you-create-an-nstimer-and-specify/</link><pubDate>Wed, 07 Jul 2010 19:23:00 +0200</pubDate><guid>https://blog.arcanelab.com/2010/07/nstimer-invalidate-when-you-create-an-nstimer-and-specify/</guid><description>&lt;h1&gt;NSTimer invalidate&lt;/h1&gt;
&lt;p&gt;When you create an NSTimer, and specify it to be a non-repeat timer, you don&amp;rsquo;t have to invalidate it after it fired.&lt;/p&gt;
&lt;p&gt;When you created a repeating timer, you send the invalidate message to it to remove it from the NSRunLoop object it was added to, and thus stopping it from being fired any more. When you invalidated an NSTimer object, you cannot use it again.&lt;/p&gt;
&lt;p&gt;More info &lt;a href="http://stackoverflow.com/questions/1583706/iphone-multiple-nstimer-troubles"&gt;here&lt;/a&gt; and &lt;a href="http://developer.apple.com/iphone/library/documentation/cocoa/reference/foundation/Classes/NSTimer_Class/Reference/NSTimer.html"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>