There was a bug in Cashculator 1.1.4 and average plan calculations. Release 1.1.5 fixes this bug. All users are encouraged to update their copies.

Hit “Check for updates…” in Cashculator’s menu or download the new .DMG from the site.

A new newsletter was also sent out to all Cashculator subscribers. Including news and Cashculator tips. Check out previous newsletters at and subscribe from the same page.

A bug was present in Cashculator 1.1.3 that could cause Cashculatorto hang in some cases when switch plan to average mode. Thanks to Dan for finding this and leading to the cause. Full release notes:

• FIX: Cashculator could sometimes hang when switching plan to Average
• Updated German localization All tutorials are now available in German
• Updated Russian localization All tutorials are now available in Russian

As usual, autoupdate from Cashculator menu or download from http://www.apparentsoft.com/cashculator/download

Cashculator version 1.1.1 has several important bug fixes and is recommended to all current Cashculator customers. List of changes:

• Fixed possible crash on Leopard – sometimes a crash occurred on 10.5 (Leopard) systems when using short horizons.
• Fixed average calculations inconsitency – In some cases average plans were calculated wrong.
• Not being able to set an average plan – Fixed a rare case where a plan couldn’t be set to be average.

Download Cashculator from: http://www.apparentsoft.com/cashculator/download

A crashing bug was reported by David Zizza in the variations drawer handling. David also suggested a small usability feature regarding loading variations. Here’s the changelog:

• Fixed: a critical bug that caused ImageFramer to crash when working with variation that used different frames.
• New: When loading designs into the variations drawer, if they were not named specifically before saving through the variations table, they’ll now be loaded and shown in the table using their file name. If the user did change the default variation name before saving, it will be shown instead of the file name. So both approaches now produces easier variation handling
• Fixed: In french localization, the save setting dialog could become too narrow, causing the buttons on the buttom to collide. Fixed by limiting the minimum width of the save dialog to accommodate the longer french text.

Download the new version from http://www.apparentsoft.com/imageframer/download.

A fix was found and implemented that deals with the issue of chopped frames in ImageFramer on Snow Leopard. See previous post for the details of the problem.

Release is expected on Tuesday or Wednesday, together with updates to Japanese translation and possibly an additional French translation.

Those in hurry to use ImageFramer on Snow Leopard before the update arrives, please contact us to get a preview version.

Version 2.3.1 (current latest) of ImageFramer seems to have an issue in Snow Leopard where the color effects (Hue, Saturation, Brightess and Colorize) will create a chopped looking frame, unsuitable for export. See screenshot below:

Be assured, we’re working on fixing this issue. Look forward to ImageFramer 2.3.2 update soon.

Jacob.

This is a bug fix and behaviour fix release. Mainly, two things were fixed:

1. Made “Controls” button only open/close controls window and not Colors panel as well.
2. Fixes crash when selecting a frame, then closing window with red button.

Both issues were reported to me by Kosta, my recently joined partner.

Wow, it took me a really long time to notice, and I feel almost stupid now.

I didn’t pay any attention but Google never brought any traffic to the Apparent Software website. But somehow it didn’t bother me as much, I was busy developing. A few days ago I noticed this and started to look into the source.

Looking at the server log files I noticed that all my responses for pages were HTTP status 404 (page not found). Apparently, Google doesn’t index requests that return code 404 (and it really shoudn’t).

I use Ruby On Rails (RoR) for my Apparent Software website and lighttpd with Fast-CGI to serve it. The easiest way to serve with Fast-CGI and RoR is setting the webapp to be the 404 error handler in lighttpd, using the following line of code:

server.error-handler-404 = "/dispatch.fcgi"

In the specific version of lighttpd web server that I was using (1.4.16) there was this nasty bug that stripped HTTP response header from the app in this case. So today I upgraded to the latest stable 1.4.19 and, voila, the response code is back to normal (200). 

Now, hopefully, Google and its lesser brothers will catch up, crawl the site, index and divert some search traffic into Apparent Software and another site I had with the same issue. I wonder how long it will take. I’ll keep updated.