Version 1.2.1 submitted to the App Store!

Yep you heard that right!! :D

A couple of my friends found some issues that needed to be addressed.
I found a couple more just prior to submitting.
But still got everything submitted this afternoon...
We'll see how quick Apple turns it around, I'm guess by the end of the week.

Now to start on version 1.3

Version 1.2.1 in Testing!

Granted no one actually reads this but myself, but fiiiiinally I got the next version ready for release.  I've given it to several friends of mine to help me test a couple critical features.  Barring any problems I should have it submitted to the app store next week! :D

Planning for new versions of Morse Elmer

Well, granted I'm writing this basically for myself, but in case any users happen to check the blog...
I'm planning on several new version of Morse Elmer.  The QST article in January 2012 really spiked my downloads.  I've had numerous suggestions for features and several bugs pointed out.
So to keep everything straight here's how I'm going to proceed:

Soon version 1.2.1 will be released to addressed a couple of bugs.  The bugs are, for the most part, fairly innocuous but at least one involves a migration of the underlying database that stores all the training results... this is something that I don't want to mess up.  So just addressing the bugs in that release will be keep the headaches to a minimum

Next I'll start working on version 1.3 this will consist of several new features, including the much requested:  type on device while training.

Lastly, I'll then proceed to version 2.0 which will extend Morse Elmer to run universally on an iPad.
I have a few other tweaks I'll plan to include but those will be surprises :D

Below is a list of what I intend on including in each release:

1.2.1 (bug fixes)

• attempting to insert a character at the beginning of a training causes the cursor to keep jumping to the end - JM 1/3/2012
• progress edit page always shows 1 char even when set for something other than 1 - JT 9/20/11

1.3 (new features)

• support local character sets - HG 1/26/12
• support training for a user supplied file/URL, etc - JM 1/10/12
• support typing in a separate window while training - JM 1/3/12

2.0 (universal app)

• Universal App

I can't promise when I'll have these versions ready, but I'm kinda itching to get some of this resolved, so hopefully soon.

Thanks to everyone whose provided feedback.

73's

KI4OWG

QST Review!

I happened to check my iTunesConnect account recently and was shocked my a huge up swing in my Morse Elmer App sales... I tracked it down to a nice review of the app in the February 2012 issue of QST (p. 98).
Thanks to all new Morse Elmer users.

I've been getting more emails asking questions and several emails making suggestions for the next version.

I've been very busy for the last 3-4 months with my day job, but I've certainly accumulated enough bugs and feature requests to start the new version of Morse Elmer.  I'll post later what I'm considering for the new version.

Any and all input is welcomed.

Please when you get a chance go back to the App Store and rate the App.

Morse Elmer does have a user(s)

I received an email today from a Morse Elmer user!! (yes they do exist...)
He was reporting a bug... a field isn't displaying properly in the Progress/Edit view...
The second field "XX chars" is suppose to show how many characters were in your training set...
It currently shows 1 all the time... the user was using the Default Training Set.

this is a hold over from version 1.1, when there was only 1 training set.
Now I have multiple training sets... and each set has a num chars used field... because you might be training with 13 characters in the default set, but only 2 characters in the prosigns set, etc...

so what to do now... I have only one field in the database for this, but two value to store.
I can actually get the the two values into a single field, but what to do with all the values everyone already has stored in the Morse Elmer DB...?!

I get to release a new version that now has to include a CoreData Migration something or other...
upgrade everyone's db to the new format.  bleh...

Well it's something to work on.

This user also made a couple of other suggestions, some of which I'll include in the next release as well.

hmmm off to do some Core Data Migration reading.... >.<