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 436263 - Unindent task unselects the task
Unindent task unselects the task
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: Normal minor
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2007-05-06 04:22 UTC by Benjamin
Modified: 2008-04-12 14:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin 2007-05-06 04:22:05 UTC
Please describe the problem:
I wanted to move a sub-task up several levels, but noticed that when I hit the unindent task button several times it only applied once. This appears to be because the task is in some way unselected on unindent. Indent is not affected.

Steps to reproduce:
1. Create three nested tasks: 1, 1.1, and 1.1.1
2. Select 1.1.1 and press the unindent task button on the toolbar twice


Actual results:
The selected task is only unindented once. The Remove Task, Indent Task, Unindent Task, Move task Up, and Move Task Down buttons became greyed out after the first unindent. Clicking off the task then back on again fixes the problem.

Expected results:
The selected task should be unindented twice. The toolbar buttons should not be greyed out.

Does this happen every time?
Yes

Other information:
Comment 1 Kurt Maute 2007-07-28 18:25:20 UTC
Just committed a patch from Maurice van der Pot which fixes the selection problem for a single task.  However, multiple task selection is still challenged in this area - only the bottom most task remains selected after unindent.

Making progress, but but remains open.
Comment 2 Maurice van der Pot 2008-04-12 14:38:23 UTC
Oops, forgot to close this bug when I checked in the final fixes (revision 884).
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.