Bingo Card Creator 1.03 Released

Well, seeing as how I had some time free today I decided to finally get off my duff and start distributing Bingo Card Creator 1.03. The main changes:

  • Vastly improved memory usage while printing. Customers who try printing 50 cards on individual pieces of paper will not see the program die on low-memory machines anymore (I hadn’t anticipated anybody would try to do this and so didn’t test it… doh?)
  • Printing is now threaded. This means that for folks with printers which are getting a little long in the tooth, the interface won’t appear to lock up for two minutes at a time. Its mostly a cosmetic improvement since I’m guessing after printing most people will go straight to the printer, but app responsiveness is generally a nice thing to have. For 1.04 I’ll consider putting in some sort of dialog to indicate the printing is actually currently taking place — maybe popup a progress bar somewhere.
  • No more flickering — I render all the pages to get printed just off the screen in a JWindow, which means that there won’t be an ugly gray flicker in front of the main application window, and it won’t lose focus.

While at least two of these had been on the back burner for a while (“Hmm, that code is ugly and inefficient… I should fix it… sometime…”), they got kicked to the front burner directly after being cited as reasons for my first return. Yay for useful feedback, especially useful feedback that doesn’t technically cost me any money (did you know that processing a return through Paypal is totally free? Yeah, I was pleasantly pleased, too, but they refund your fee after you do one.), although it did cost a sale.

Explore posts in the same categories: Uncategorized

3 Comments on “Bingo Card Creator 1.03 Released”

  1. cja Says:

    After what you said in your post about how returns should be handled, maybe you should email the person who returned it and tell them they can have the new version free.

  2. Patrick Says:

    I like your way of thinking, but for reasons which are specific to this customer won’t be doing that this time. (The bugs were the lesser of two reasons for the return, the main reason was a feature request which is something along the lines of “This hammer would be perfect if it just worked for screws, too” — one which I cannot easily accomodate and without which the program just isn’t the right choice for him.)

  3. Jason Says:

    I’m curious: I think I read you are developing on eclipse.
    Why did you not go with SWT over swing? Any special reason? I ask because I develop eclipse RCP apps using SWT.

    Great blog, please keep it up!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: