When we originally developed SCWB, we had to suppress the default keyboard so we could provide our own with the custom buttons necessary to do what the app needs to do. iOS 3.2 threw us a bit of a curveball. It happened again with iOS 4.

In iOS 3.0.x thru 3.1.x it was a bit of a hack. With the release of iOS 3.2 for the iPad, Apple decided to change how that hack had to work, so we scrambled (and by we, I mean Develish) to find a new hack. We got that corrected ahead of the release of the iPad. With the release of iOS 4, Apple changed this once again, but in a good way. They actually provided an accepted method to suppress the keyboard. Very cool. We again were ready in time for the release of iOS 4. What is not so cool, is the troubles this led to in updating the app on some iPads (We still can't figure out why it worked on some and not on others. No common thread at all) and legacy devices, like the iPod Touch 1G.

Develish did an awesome job providing for all three instances in the code, but that doesn't mean much if said awesome code can't be installed on the devices in question.

I'm pleased to report that after much screwing around in XCode playing with build settings, I found the magic combination that works on all devices. There were some very interesting side effects if some options were chosen, including a permanent full screen version on the iPad. (No, you don't want it. It reveals some of our magic tricks, and hence looks ugly)

While doing all of this dinking around, Develish discovered that in iOS 4, when you quit the app and it dutifully goes to the background, even though we never coded it to do so (tricksy Apple), if you then force quit the app from the app switcher, it lost all of the settings we were saving. (like last used dial positions, last entered message, etc.) So, he wrapped up that routine and called it when the app goes into the background instead of on quit, and voila! It finally behaves. Version 1.0.4 has been submitted to Apple and should be available soon.

I also wanted to take some time to address some of the comments we've received in the App Store about the app. (Double-edged sword that. Great way to get criticism, but no way to respond to it. Aggrivating to say the least)

shbmwmc: Version 1.0.4 will fix your install problem on your iPod 1G. If it doesn't, please let us know through the contact form on the site. Thanks for letting us know about the problem. We had stopped testing on that architecture. We will keep testing on it as long as we can now that we know someone using our app is relying on it.

dmac-ct: I responded to you in email addressing all of your concerns. I'm just putting a note out here to thank you for your emails, to apologize once again for not responding to you in a timely manner, and to let everyone else thinking the same thing know that the app was specifically designed to emulate the real cipher devices of old, so dynamic dials are beyond the scope of our intention or desire. Sorry.

James "Psy" Kocsis: I'm sorry you went to so much trouble for a message. We included copy/paste specifically to avoid making people write it all down then type it in manually as you apparently did. Purists are welcome to do that, but we knew in this day and age of "Gimme now!" it just wasn't feasible to make everyone do that.

Janekg (of Australia): I honestly don't know what to say. We provided step by step instructions in the app that can be enabled/disabled at any time as well as full walkthrough text in the info section. If you have suggestions to better explain the app's use, we are interested in hearing them! I'm sorry we failed you.

Finally, to ManiacFive, BASboy, Lucky Luxy, Joe in Los Angeles, kd6ftr, deekayoh007, annesarbor, rgunther, CNJKevin, BaranM, and Silverleaf aka Hellfire: Thank you very much for the kind and often amusing words! We appreciate it!