#1584 Slow operation when save after each change ticked

[John F Dawson]

Actually Release 1.4.2 but that is not available above.
I noticed that as I got a bigger task database Task Coach got very slow - 4-5 second delay after every mouse click.
I finally figured it out. The default "save after every change" setting seems to be the problem. A save seems to be performed when you do things like expand or collapse tree items or simply open a task. With ~240 tasks this is quite unusable.
Unchecking the "save after every change" box seems to bring the performance back.
This to me seems a bug - surely saving the database every time you expand a tree item or open a task is not really necessary if it causes such problems.

[Michael]

I've got the exactly same behaviour, but with only a few douzen tasks and version 1.4.3

[Aaron Wolf]

So sorry nobody replied to this ticket originally!

A decade later though, we're happy to be announcing that Task Coach is now updated to Python3 and development is finally active again, thanks to new volunteers. The project has now moved to https://github.com/taskcoach/taskcoach

I'm using it myself, and things are working better than ever. Packages are available for some common Linux systems and for Windows (note that it isn't recognized by Windows Smartscreen but can be installed by accepting the warning anyway)

We'd love to have you test the updated program, and post any issues that arise there at GitHub

We won't be continuing with SourceForge, just clearing out old issues and letting people know about the move

Cheers