SlickTasks Tiny Bug: renaming a task with sub-tasks

1 view
Skip to first unread message

Michael

unread,
Nov 5, 2009, 9:59:17 AM11/5/09
to MindBerry
Using version 1.1.2.1 of SlickTasks

What I did: renamed a task that had sub-tasks.

What I expected to happen: the new name would appear.

What actually happened: the old name appeared!

So, I tested it in 4 scenarios:

First, a task with sub-tasks that were collapsed-from-view. Changed
the name of the task using the in-line editor (Enter key). The old
name re-appeared as soon as I hit enter. When I expanded the task to
see the sub-tasks, the new name came back. When I re-collapsed the
task, the old name was there.

Second, a task with no sub-tasks. Changed the name using the in-line
editor and the new name appeared, as expected.

Third, like the first but the sub-tasks were expanded. Same basic
result. The new task name appeared while the sub-tasks were
expanded. The old name appeared when I collapsed the task.

Fourth, like the first but using the full editor (roller-button).
Same results as with the in-line editor.

When I "closed" (not shutdown) and re-opened SlickTasks, the naming
problems remained. All the old names showed when the sub-tasks were
collapsed and the new names showed when the tasks were expaneded.

**Workaround** When I "shutdown" and re-opened SlickTasks, the naming
problems were fixed. The old names disappeared and the new names
showed both when the task was expanded or collapsed.


Mike

Michael

unread,
Nov 5, 2009, 11:49:24 AM11/5/09
to MindBerry
This bug may relate to the "show number of collapsed tasks" option.

This option was set to "Yes" for all the cases above. When I set it
to "No," the renaming worked just fine.


Mike

Dat Luong

unread,
Nov 5, 2009, 12:35:20 PM11/5/09
to mind...@googlegroups.com
Thanks, Mike. SlickTasks uses caching to improve performance and the cache is not updated when renaming a task (the cache is used when "show number of collapsed tasks" option is "Yes"). Of course the new task summary is still saved, and you can get the cache updated again by adding a new child task to it :)

The bug fixed.
Regards,
Dat

Michael

unread,
Nov 7, 2009, 8:42:11 PM11/7/09
to MindBerry

> you can get the cache updated again by adding a new child task to it :)
>
Yes, that makes sense.

> The bug fixed.
> Regards,
> Dat

Thank you, Dat.
Reply all
Reply to author
Forward
0 new messages