After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141117 - Tree expansion state gets out of sync in Resource Usage view.
Tree expansion state gets out of sync in Resource Usage view.
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: General
unspecified
Other All
: Normal minor
: 0.12
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2004-04-26 05:36 UTC by Lincoln Phipps
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Sample very small project. (2.19 KB, text/plain)
2004-04-26 05:37 UTC, Lincoln Phipps 		Details

Description Lincoln Phipps 2004-04-26 05:36:42 UTC 
Do this - Open a project with multiple resources (e.g.2) allocated and a summary
task (e.g. 1.) with children (e.g. 1.1 1.2 etc),
Remove the 1. task (parent).
Switch to Resource Usage View.
Click Undo button.
The left hand frame (table of resources/task names) table doesn't automatically
expand though the right hand frame (bar graph rows) does.
Comment 1 Lincoln Phipps 2004-04-26 05:37:50 UTC 
Created attachment 27090 [details]
Sample very small project.
Comment 2 Xavier Ordoquy 2004-04-28 13:01:24 UTC 
Isn't it a duplicate of #141120 ?
Comment 3 Lincoln Phipps 2004-04-28 16:14:52 UTC 
No - though it may be in the code BUT it looks completely different in the
actual faulty display AND with this bug you can fix up the display by
expanding/collapsing resources whereas 141120 stays broken forever until you
exit Planner and go back in to Planner project.
Comment 4 Lincoln Phipps 2004-04-30 08:17:11 UTC 
I have a patch to fix this BUT I've broken my patch so need a bit more time to
re-implement the signals.

What I'm doing is when I get a project task-inserted or task-removed signal I
then generate model signals.

The view watches the model for task-added or task-removed signals and when added
it simply expands the view and when a task is removed it collapses the view.
This is the easiest way to do this and seems to keep the display sane. I got
carried away and tried to just play with individual rows but broke it from what
I had working so I'll go back a bit :)

Lincoln.
Comment 5 Richard Hult 2004-05-09 23:37:42 UTC 
I don't agree that it's sane ;) We should at least just expand/collapse the node
that the task is added to/removed from.
Comment 6 Richard Hult 2004-06-18 22:22:32 UTC 
Was an easy-fix, totally unrelated to undo.