To do this, simply type:

dig domaintolookup.com +trace

You can hear more here:

What does iPhone OS 3.0 Mean for Your Apps (WSP Online)

If you’re like me, you like to leave on the defaults unless absolutely necessary. I had an issue where I added an image view to the scroll view in Interface Builder.
The image view then had an image added to in code. I resized the content view of the scroll view in code to be the same size as the image view (which you have to do
in order to get it to scroll).

Unfortunately, when an image larger than the scrollview was used, it went off the top of the scroll view by about 30px. I thought its origin was using the main view,
instead of the scroll view’s frame, but after modifying various properties I had no luck – and strange results, with the image always returning to about 30px higher than
the scroll view content area.

After trying to resolve things programattically, I resorted to Interface Builder again. I tried any number of properties on the scroll view to get its content
placed at its origin. It turns out that, by default, a UIImageView has a default “Mode” of center. That affects its alignment in its parent view. This ain’t
HTML kids, it is the elements themselves who decide how they are aligned in their parent elements. So, I just change the “Mode” to “Top Left”, and Robert’s your mother’s
brother.

The code for getting the scroll view to scroll (just FYI) is included below. If thisImage is bigger than the scroll view in any dimension, it will let you scroll
in the corresponding direction – but if it’s the same size or smaller, no scrolling is possible in that direction. Pretty nice. self.scrollView, by the way, has
only the default Interface Builder properties.

CGImageRef imageRef = thisImage.CGImage;
CGFloat width = CGImageGetWidth(imageRef);
CGFloat height = CGImageGetHeight(imageRef);

[self.scrollView setContentSize:CGSizeMake(width, height)];

The code to load the sending view (from the main app delegate) was:

- (IBAction)sendContact:(id)sender
{
	DataController* dc = [DataController sharedInstance];
	dc.contactRecord = (NSMutableDictionary*) [self.userDefaults dictionaryForKey:@"currentUser"];

	SendingViewController *sendingViewController = [[SendingViewController alloc] initWithNibName:@"ReceiverView" bundle:nil];
	[self setBackButtonText:@"Back"];
	[self.navigationController pushViewController:sendingViewController animated:YES];
	[sendingViewController release];
}

The code for the receiving view was:

- (IBAction)receiveContact:(id)sender
{
	ReceivingViewController *receiverViewController = [[ReceivingViewController alloc] initWithNibName:@"ReceivingView" bundle:nil];
	[self setBackButtonText:@"Back"];
	[self.navigationController pushViewController:receiverViewController animated:YES];
	[receiverViewController release];
}

On load, I could _swear_ that nothing happend with the DataController’s contact record. But something screwy was going on. When I hit “send” first (on app launch), hitting “receive” worked fine (you could navigate back with no worries at all). However, when you hit “receive” first, going back only got the navigation bar to change, while the receive view was still visible.

It took ages, but setting contactRecord in the DataController shared instance fixed the problem.

The thing is, the view loaded just fine, no worries at all. No errors or warnings occured… and I wasn’t using contactRecord for anything on the view. So why did it behave like it encountered an error? I searched the code, and I was setting a label (which didn’t even exist on-screen anymore, it was an unused IBOutlet UILabel) to something contained in the DataController. Why it didn’t error properly, and why that stopped the view from unloading properly is completely beyond me… The NavigationBar operates (somewhat) in isolation from the views inside it, so if a view gets stuck (but not the Nav control) you can find yourself in a very weird situation.

So, my advice to you is:

• It ain’t the same until it’s _exactly_ the same.
• Just because it doesn’t error, doesn’t mean it hasn’t produced an error.
• If you can at all avoid it, don’t copy paste entire files. Best to start empty and include the stuff you need instead.

They are also into working out how much time you save by using their device – which they use as a global tally to show how much time the world is saving by removing the need to untangle headphones.

This is a really novel idea and a cool device.  Head over to BudTrap.com now to start saving your tangle time.

myWebView.opaque = NO;
myWebView.backgroundColor = [UIColor clearColor];
[myWebView loadHTMLString:
@"<html><body style='background-color: transparent'>
       Content Here</body></html>" baseURL:nil];

The above works in 2.2.

NSString* escapedUrlString =
   [unescapedString stringByAddingPercentEscapesUsingEncoding:
                        NSASCIIStringEncoding];

Then just use the escapedUrlString in your NSURL object and you’re on your way.

One gotchya that I discovered while attempting to access Webservices was ensuring that you actually expose your Apex class as a webservice:

global class myClass {
    webservice static Double getTotalSales() {
        Double globalTotal = 0;
        // Code goes here....

        return globalTotal;
    }
}

Additionally, on the PHP end, ensure you put the name of the class you are attempting to access in the NAMESPACE when you put your session ID in the salesforce header (see below).  The below example assumes you have already connected to salesforce using the PHP Toolkit and the connection is in the $sfc variable:

    $sessionID = $sfc->getSessionId();

    $wsdl="soapclient/myClass.wsdl.xml";
    $NAMESPACE = "http://soap.sforce.com/schemas/class/myClass";

    $sforce_header = new SoapHeader($NAMESPACE, "SessionHeader",
                        array("sessionId" => $sessionID));
    $client = new soapclient($wsdl);
    $client->__setSoapHeaders(array($sforce_header));

    try{
        $result = $client->getTotalSales();   
    }
    catch(Exception $e) {
        print "<pre>";
        print_r($e);
        exit;
    }

If you forget that step, you can end up with a [soapenv:Client] Element {}item invalid at this location error which is bloody hard to debug. Trust me.

    NSNumber *valueForDisplay = [NSNumber numberWithDouble:
              [self valueForDisplay:clockName]];

    NSNumber *totalDays = [NSNumber numberWithDouble:
             ([valueForDisplay doubleValue] / 86400)];
    NSNumber *totalHours = [NSNumber numberWithDouble:
             (([valueForDisplay doubleValue] / 3600) -
              ([totalDays intValue] * 24))];
    NSNumber *totalMinutes = [NSNumber numberWithDouble:
             (([valueForDisplay doubleValue] / 60) -
             ([totalDays intValue] * 24 * 60) -
             ([totalHours intValue] * 60))];
    NSNumber *totalSeconds = [NSNumber numberWithInt:
             ([valueForDisplay intValue] % 60)];

The above assumes that valueForDisplay contains the total value in seconds.  Enjoy.

I wanted to have my complex app resource directory structure replicated in the “Resources” directory of my app – so that all my images, sound files and html files were stored in logical locations – except they always ended up in the base directory of the bundle!

To solve this problem you have to choose the “Create Folder References for any added folders” option when you drag your folder into the Xcode project:

This fixes the problem!  You can then reference your files with the path to your directories included:

NSString *filePath = [[[NSBundle mainBundle] resourcePath]
                stringByAppendingPathComponent:@"pathToMyFiles"];