Free is good! But Dextronet has recently sent me this (I'm a registered user of the Pro version):

We've recently launched new Ultimate edition of Swift To-Do List. Compared to
Professional, it adds these new features:

1) 100 new tree icons (so there is no 244 in total in Ultimate!)
2) Two-line displaying of too long task names
3) Spellchecker for notes and memos
4) Multi-level numbered lists in notes and memos (outlines)
5) Other extra Ultimate-only features that will be added in the future as free Ultimate-only upgrades.

I started with the Standard version in 2007, later upgraded to Pro. That was already quite expensive. Now in a classic bait-and-switch, they are offering a new "Ultimate" version... which has more icons and a spell-checker and a promise... for $199.95 (regular price).

I've noticed I have been avoiding using Swift To-Do List, because of its agonizingly slow startup and general sluggishness while editing notes (.Net again!), un-backup-able database (while the app is running, and it should be running all the time) and its malicious splash screen, which always shows on the active monitor only to block your view for about 10 seconds. (IMO this is literally malicious, as in, the programmer had to expend some effort to make sure the splash screen always shows on the active screen, because every time I've launched the app I so want to look at it again, every time in the five years I've been using it. Can't disable the splash screen in program options. This is one of the things that make me wonder sometimes :-) Oh, and since a version a few months back it installs not in Program Files, but under Users/AppData, which is still wrong even if Chrome does this too.

Knowing what I know now, I'd get it for free, but I won't be giving Dextronet any more money in the future.

New release March 25 (Version 1.1.2)

This release fixes important bugs. Please download and install this release, especially if you are using version 1.1.1 (published February 21).

See the top post in this thread for download links.

New in this release:


FIXED: A significant bug that would cause loss of certain clips when Echo performed database maintenance. This bug affected only certain installations, but was quite severe when it occurred.

FIXED: Minor change to allow Echo to paste clips into certain applications with non-standard windows that do not automatically regain focus (e.g. Stickes). Echo should now be able to paste clips into such applications, but only if Echo runs minimized and only if it is activated by the activation hotkey (not with the mouse).

To Dan and everyone using the latest version of Echo (1.1.1):

Please read! Yep, we have a red alert here.

There is an important bug in this version that causes some data loss under certain conditions. As a result of the bug, some clips lose their data and become unusable when Echo performs database maintenance. The bug was introduced in version 1.1.1 and affects only recent installations, but just in case I ask everyone using Echo to apply a temporary fix.

Please do the following in Echo:

• Click Tools -> Available clipboard formats.
• Without changing anything in the dialog box, click OK.

This will refresh the list of formats stored in the database, and will add the required CF_TEXT and CF_UNICODE formats if they are not already listed in the database.

As an additional precaution, you can also temporarily disable automatic maintenance in Echo by doing the following:

• Click Tools -> Preferences -> Database maintenance.
• Set AutomaticMaintenance to False.

This should prevent any further data loss until I release an update (in one or two days).

How do you tell if you are affected by the bug?

You are affected, if you experience the bug described in this post:
https://www.donationcoder.com/forum/index.php?topic=27849.msg282383#msg282383

You are affected, if the latest version (1.1.1) is the first version you ever installed, or if you have deleted and re-created the database since installing this version.

Apologies! And thanks to Dan for reporting this. A fix is coming, but for now, the two procedures described above will keep everyone's installation safe from the bug.