Mar 28, 2012
I thought I was smart when refactoring some code in DTAboutViewController to use block-based animations. Turns out that I had not considered backwards compatibility for 3.x when doing that simple change. This caused some unlucky users (still on iOS 3.1.3) to get the update pushed via iTunes, but then finding themselves unable to launch the app.
I do plan to cease supporting 3.x sooner or later, but not like this. The proper way is to raise the deployment target when implementing features that require 4.x. This way people unwilling (or unable) to update their devices just won’t be receiving those new updates but will still be able to continue using the old version.
- Fixed: Incompatibility with 3.x causes app to crash
- Added: Alert when user tries to send support e-mail but has no account configured
- Fixed: Tapping on today button in cycle view would show the wrong day in cycle view.
- Fixed: Tapping on the calendar button in Wheel View would lead to the wrong day in calendar view (in some time zones)
The update has been submitted to Apple and should be available soon.
Update April 4th: … the update is now available on the App Store.
Mar 15, 2012
I did a quick fix for Linguan after several users complained about the strict slash-escaping that we had introduced in 1.0.4.
Linguan un-escapes all texts it reads from strings files so that they can be displayed correctly. You don’t want to have to deal with backslashes in the editor. Now on writing I had thought it to be a good idea to also escape everything, including question marks, backslashes and single quotes. It was a bad idea to do that because this unduely changes the tokens and translations.
Translators (the sad kind without Linguan) would be confused by having to deal with lots of \’ in the text. And there where some reports of the localized string loading functions not being able to find the key. Not always, but this is clearly not what we wanted.
This update relaxes the escaping on writing to the extent that only double quotes and invisible characters are now being escaped.
Mar 06, 2012
This release fixes the crash on iOS 5 that I had in all my apps using the version of DTAboutViewController from before iOS 5 was released. I’m sorry for having procrastinated so long on updating SpeakerClock, but I had forgotten about this issue until a user reminded me of it via e-mail.
The update has been submitted to Apple and we hope to have it available on the app store in about 5 days.
Update March 10th: … and it’s approved and available for download.
Feb 19, 2012
This is a hot fix release addressing several issues that users found. You now have a new option to decode unicode sequences with two backslashes on loading strings files or scanning source code. Decoding and Encoding of slash escapes now uses the functions provided by genstrings2.
Feb 08, 2012
Here’s another maintenance release fixing a crashing bug in the About section.
- Fixed: Crash on trying to open usage instructions
- Added: More detailed explanation of accuracy and filter settings
This update, like the one before it, goes out for the paid version of GeoCorder first. If the issues are resolved once this comes into the store then we’ll update the ad-sponsored version, too.
Update Feb 11th: The update has been approved.
Feb 03, 2012
This is a maintenance update. There was a bug in DTAboutViewController which caused a crash under iOS 5.
- Fixed: Crash on iOS 5 when opening About Section
The update has been submitted to Apple for approval.
Update Feb 8th: Ready for Sale. It should be available shortly.
Jan 16, 2012
Besides fixing several bugs reported by users this release focusses on implementing a new custom-built super-charged strings scanner.
- FIXED: missing strings file no longer aborts import
- FIXED: added – Button for deleting tokens
- FIXED: deletion of wrong row
- FIXED: over-escaping of \ on writing strings files
- FIXED: wrong token name updated on enter key
- FIXED: search filter not reset on adding a new token
- FIXED: Previous/Next buttons in wizard cease to function
- NEW: replaced genstrings with high-speed custom implementation (>20x speed improvement)
- NEW: support custom localization macro prefix
This new version does no longer support 32-bit because the new strings scanner was implemented using ARC. We hope that this does not inconvenience any of our existing uses. But then again, serious developers are on a 64 bit machine anyway since Snow Leopard…
The new version has been submitted to Apple today.
Dec 06, 2011
The second hot fix pack for Linguan 1.0 fixes a couple more issues that some of our (mostly) happy customers reported.
- Fixed: Translations will no longer get trimmed
- Fixed: Problem opening projects with absolute file paths
- Fixed: Table did not update on deletion of token
- Changed: Extended duration of “no new tokens found” HUD
- Changed: Enter key now opens selected recent project in welcome screen
If you haven’t done so please post your feedback on iTunes. To be able to add additional features to Linguan we need to have sufficient sales. And for that we need your positive reviews, high rating and that you tell other developers about Linguan.
Today is the best day for them to also get a copy because: As a Thank You for your interest in our app we reduced the sale price by 50% until the new version gets approval by Apple.
Nov 18, 2011
My partners at BytePoets have been causing their keyboards to emit steam from walking through 26 issues that we identified on the 1.0 release just 9 days ago. Almost all had been identified as typical “oh shoot” elements, mostly items that you only find when people begin to actually use your software. Also I was able to smuggle in one or the other new feature since I consider “user confusion” also as a form of bug that you should hot fix if you can.