Fixed in rev. 762
Tasks with multiple parents should now be handled normally. (bug #585275)
There's still one case where we will return a random parent because we
implement the pygtk on_iter_next and cannot do anything about it.
(it means that now FilteredTree supports multiple parents. But Tasktree does
perfectly because it implements TreeModel which cannot support that)
Currently, a warning is displayed but it doesn't look like it affects the way
GTG is running.
Please report any bug related to tasks with multiple parents.
In fact, I was fearing to have to make huge major changes in our
infrastructur (with virtual nodes and stuffs like that.) I was able to
do that of the FilteredTree level in a very elegant way. Thus, I prefer
to wait to see if the iter_next in the tasktree is going to be a big
problem or if is it going to be unnoticed.
** Changed in: gtg
Status: In Progress => Fix Committed
--
Subtasks with multiple parents are shown randomly
https://bugs.launchpad.net/bugs/585275
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.
Status in Getting Things GNOME!: Fix Committed
Bug description:
The parent for which the subtask is displayed is choosen randomly.
It should appear for all the parents
_______________________________________________
Mailing list: https://launchpad.net/~gtg
Post to : [email protected]
Unsubscribe : https://launchpad.net/~gtg
More help : https://help.launchpad.net/ListHelp
