Archive

Archive for January, 2011

Meter Readings 2.7 now available

January 22, 2011 Comments off

Fixed a bug introduced in version 2.6.1 that caused the app to crash on devices running iOS 3.1.3 or earlier.

By popular request, added support for syncing between devices using Bluetooth. This feature is included as part of my Backup and Restore in-app purchase, and it lets you send a backup file directly from one device to another (e.g. your iPhone to your iPad).

Account Tracker 2.8.2 now available

January 15, 2011 Comments off

Fixed two bugs introduced in version 2.8: the first where edited occurrences of recurring transactions were being shown even though they were after the end date of the series, and the second where one-off transactions were not being shown if they were previously recurring transactions and the first occurrence had been edited. These are both pretty obscure circumstances and they only affected about 10 people in total.

Added an option to the blue button to the right of each transaction where you can quickly adjust the balance. This feature will be useful for those of you who don’t want to keep track of each and every bit of spending, but need a way of adjusting the balance at the end of the month (or other frequency).

Added support for searching by cheque/check number.

Tidied up the budgets screen – there are now just three sections, for spending, income and transfers.

Added a setting to prioritise future transactions – if this is ON reconciled transactions will be shown in grey and un-reconciled/future transactions in black. Turning it off will reverse these colours.

Added a link to my Known issues (i.e. support) page in the settings. If you encounter a problem with the app, the best thing to do is to check this first as that is where I will post information or workarounds.

Meter Readings 2.6.1 now available

January 13, 2011 Comments off

Improvements to the UI.

Improved the CSV export and import features.

Relaxed the restriction where you couldn’t add new rates if they came into effect in the future.

Made the user guide more accessible in the settings screen, and also added a link to take users to my known issues (support) page. Also added documentation for iTunes file sharing.

Minor bug fixes.

Account Tracker 2.8.1 now available

January 10, 2011 Comments off

This is a bug fix release to fix two issues: the crash introduced by 2.8, and a problem with alerts on early devices.

Account Tracker 2.8 now available

January 6, 2011 Comments off

Happy New Year to you all! Please read this fully as you need to be aware of a BEHAVIOUR CHANGE introduced in this release to do with opening balances.

As with all updates, please TAKE A BACKUP and EXPORT this off your device before proceeding.

NEW FEATURES
Split transactions – lets you use multiple categories against one transaction, and is supported for non-recurring transactions only (I might partly relax this restriction later, but it is quite complicated). Split amounts will be used in budgets and per-category reports, whereas the transaction amount will be used everywhere else. Splits can be enabled per transaction by selecting the new Category button on the transaction screen.

Notes per account – in the account settings, you can enter any text that you want to associate with that account.

Quickly select the Details field if you enter the Category first. Previously this only worked the other way round.

When searching an account, you can now search on the transaction amount.

In the reports, when selecting a more detailed view (the small i button at the top left of the screen), you can now sort the list alphabetically as well as by reducing amount.

CHANGES
Per-account opening balances have CHANGED. Instead of a separate “opening balance” transaction with a date, I have removed this and you now set the opening balance (without a date) in the account settings. This change should be transparent to most users, HOWEVER it is possible that you might have created transactions for an account prior to its old opening balance date. Previously these transactions would have been ignored, but they will now show up and will affect your running balance. There wasn’t an easy way to automatically fix this, so you might have to manually go and delete these early transactions, including the old Opening Balance transaction (which will have been set to 0).

Instead of highlighting the most recent transaction, I now highlight the most recent DAY in blue. This is done in the section header (when grouping by day) or the date (when grouping by month).

To help distinguish between reconciled and un-reconciled transactions, transactions are now displayed in two colours: gray or black. If your default lookahead period is off (i.e. you aren’t really interested in future transactions), I use black for reconciled and gray for un-reconciled. For any other lookahead period I use gray for reconciled and black for un-reconciled. If you hide reconciled transactions, all un-reconciled transactions will be shown in black.

CSV export and import improvements – there have been some reported issues with Excel not importing my CSV files (although you could always manually import them). Hopefully I have now fixed this issue. If anyone is still having problems, PLEASE use my support pages and get in touch.

Moved the user guide and tour to be more accessible from the Settings screen. In the user guide I have added links for leaving a review on iTunes. If you like my app, please consider doing this – it is very much appreciated!

BUG FIXES
Recurring transactions where you have edited an occurrence to be earlier than expected might not have been picked up in the Budget screens, or when drilling down to individual transactions in the Reports screen.

Exporting your data and settings from the free to the full version was not working on devices running iOS versions 3.1.3 and earlier.

Selecting weekly or fortnightly budgets or reports caused the app the crash if your region setting is Chinese.

Account Tracker 2.8 and opening balances

January 3, 2011 Comments off

In version 2.8 I have changed the way I handle the opening balance of an account, mainly because the old way added complexity, and it was a bit confusing not being able to create transactions when you wanted. Instead of there being an opening balance transaction, with a date and an amount, I no longer use the date, and the opening balance itself has moved to the account settings.

For most people this change will be completely transparent – the first time you run 2.8 I automatically migrate the opening balance to the account settings, and remove the opening balance transaction. Your balance will be correct and all will be well.

However, some people might have created transactions that occur before the old account opening balance date. This could happen if previously you decided to move your opening balance date forwards past a bunch of transactions. With the 2.8 update, these previously hidden transactions will re-appear and more importantly they will affect your balance.

For various reasons it was too dangerous to try to clean this up for you, so I thought it best to present the data and let you decide what is best. If one of your accounts is affected, when you view the account you will see the message “Opening Balance. This is now set in the account settings, however for this account one or more transactions happen BEFORE the old Opening Balance date. Since these now affect your balance, you should check and possibly delete these old transactions, INCLUDING the Opening Balance transaction itself”. If you scroll to the oldest transactions in your account, you will see one or more followed by a transaction called Opening Balance with an amount of 0.

You can now do one of two things – either leave the old transactions in place, but adjust your opening balance in the account settings to correct your running balance. Or simply delete each of these old transactions and your balance should fix itself.

Either way you should also delete the opening balance transaction, otherwise you will see the warning message every time you view that account.

I do apologise for making this change, and I wouldn’t do it if the benefits weren’t there in terms of user simplicity and code maintenance.