put it someplace warm and dry, and DON'T try to turn it on until at least a week has passed since it's been washed. You *might* be lucky.

Use a spray air can to help dry it out. Also after a few more days if it is still dead, you might need to bite the bullet and plug it in to give it a power jolt.

thanks... but one more thing. before i put my ipod in the laundry, the battery was completely dead. i dont know if that changes anything. and also when i got it out of the washing …

pry it apart and let it dry - i doubt it'll ever come back though as a normal iPod has a hard drive which don't do well at all with water.

to be optimistic, you might now have a really cool looking paperweight!

i hope you haven't tried to plug it in since it got wet (looks like you would need to since the battery was dead before the incident). wait another 4-5 days and leave it in a dry …

Quote: Originally Posted by vinster pry it apart and let it dry - i doubt it'll ever come back though as a normal iPod has a hard drive which don't do well at all with water. …

Quote: Originally Posted by Mastrap He's got a nano. And don't open it, there's no need for that. just let it dry for a couple of days, then try and plug it in. There have been…

thanks for the advice. its been 4 days already... should i wait a bit longer to try and turn it on? or should i wait a bit longer... if nothing works and i know its broken, should …

i think tomorrow im going to plug it in...

Quote: Originally Posted by janejane13 i think tomorrow im going to plug it in... Should be long enough to know if it's going to recover. Good luck!

didn't work. i tryed it over and over again and it still didn't work. so i think im just going to send it in to apple and see what they can do when i pluged it in to the charger i…

bummer

okay well i ordered the box thingy off the apple site so i can sen it in to apple and they will fix it... i hope im doing the right thing.

I found a very nice image viewer, which unfortunately wasn't a universal binary. However, the source was availible as an xcode project, so I downloaded that. Sadly, it doesn't bui…

You probably need to upgrade your target and make sure you're using an installed GCC binary.

Embarrasing, but I know too little about Xcode to understand what you meant (I looked at the targets and they only seem to describe a normal build process, with no indication of wh…

Ah; sorry. You need to choose "Project -> Update All Targets", and then Get Info on the updated target (I'm guessing there's only one target in the project before the update), g…

Thanks so much for the help! It compiled now, and with warnings, as you said, but it worked! And the application is snappy too, really nice and exactly what I wanted. The only th…

The warnings are compiler errors, not runtime errors. Compiler errors just check things that might not be safe, but actually could be.

What Ghoser said; those warnings could easily be gotten rid of in a few mintues. The compiler doesn't really need to know whether those methods exist or not, though, since Obj-C m…

Well, it looks like there might be some broken assumptions about return types there. Also, missing [super dealloc] will cause memory leaks.

I admit I didn't read through all the warnings when I built it (since I didn't really care to use it), though the missing method declarations did strike me as a bit lazy. ...Altho…

When I was compiling this program, those errors were the result of including Foundation.h instead of Cocoa.h in the files. Switching the two let the program compile. Let me give th…

Weird, I replaced all references to Foundation.h with Cocoa.h as well, and it worked. I must Google as to why that is. I also added the [super dealloc] calls as suggested, and it c…