This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 139873 - Task list should use selected project scope if no main project is selected
Summary: Task list should use selected project scope if no main project is selected
Status: RESOLVED DUPLICATE of bug 166780
Alias: None
Product: platform
Classification: Unclassified
Component: Action Items (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jan Peska
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2008-07-14 13:29 UTC by Petr Jiricka
Modified: 2012-03-29 18:19 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2008-07-14 13:29:31 UTC
1. With a fresh user dir, go to the New Java Application wizard
2. Uncheck the Set as Main Project button
3. Click Finish

=> Task list does not show any entries, because it is by default set to "main project and projects it depends on" scope,
and there is no main project. When you switch to Current File scope, one task is displayed (TODO). I would expect that
this task will also be displayed when in "project" scope. 

Suggested solution: When no main project is selected, the middle scope should be changed to "selected project".

I think this is a real usability problem, so entering as a P3 usability defect.
Comment 1 Stanislav Aubrecht 2008-07-14 13:33:21 UTC
what does hie think about this?
Comment 2 jrojcek 2008-07-14 15:38:13 UTC
I would rather suggest to change the function of the first button from Main project to All projects. Not just when there's no main project set, but as a 
permanent change.
Comment 3 Stanislav Aubrecht 2008-07-14 15:57:23 UTC
you mean make the default scope 'all opened projects' instead of 'main project', right?
Comment 4 Jesse Glick 2008-07-14 21:04:18 UTC
I would suggest just deleting the "main project and projects it depends on" scope. It is a pretty complicated concept.
Is there a compelling reason for it to exist? Why wouldn't you just use "all open projects"?
Comment 5 Stanislav Aubrecht 2008-07-15 09:03:37 UTC
good point, usability study shows that 'main project' is a strange concept for php developers anyway
Comment 6 Petr Jiricka 2008-07-15 12:46:49 UTC
>  Why wouldn't you just use "all open projects"?

Could performance be an issue? I can imagine that limiting the scope to the current project could improve performance.
On the other hand, "all open projects" could be the default. 
Comment 7 Stanislav Aubrecht 2008-07-17 12:35:54 UTC
fixed - 'opened projects' is now the default scanning scope

9fb439d8589e
Comment 8 Petr Jiricka 2008-07-18 09:28:12 UTC
Thanks - this is definitely an improvement, however the behavior is still not fixed completely, because when I have no
main project, and I manually switch to the middle scope (main project + open projects it depends on), it does nothing
and is useless - I would expect it to show tasks for the current project. 

Reopening as P4 defect.
Comment 9 Stanislav Aubrecht 2008-10-22 14:06:50 UTC
'main project' scanning now uses the 'current' project (if any) for task scanning
Comment 10 Petr Jiricka 2008-10-22 16:10:04 UTC
There is still one minor issue - reopening. Steps to reproduce:
1. Open/create a project and make sure no project is set as main
2. Switch the tasklist scope to "all opened projects"
3. Hover over the middle scope to display the tooltip - the tooltip says:
"Show tasks for the main project and for the opened projects on which it depends

This tooltip should not refer to the "main project".
 
Comment 11 Jan Peska 2011-10-27 08:23:37 UTC
(In reply to comment #10)
> This tooltip should not refer to the "main project".

You would prefer to show two different tooltips if the main project is set or not set?
Comment 12 Petr Jiricka 2011-11-01 08:33:28 UTC
I personally would, but this is mainly a question for Jano.
Comment 13 Jan Peska 2011-11-28 14:08:14 UTC
*** Bug 109549 has been marked as a duplicate of this bug. ***
Comment 14 Jesse Glick 2012-03-26 19:12:20 UTC
Needs to be reevaluated in light of bug #166780.
Comment 15 Jan Peska 2012-03-29 13:43:37 UTC
This issue is not valid anymore, since the changes mentioned in http://wiki.netbeans.org/OldTasksWindow were implemented.

fix http://hg.netbeans.org/core-main/rev/ccfe6270b994
Comment 16 Petr Jiricka 2012-03-29 14:32:04 UTC
Thanks, verified.
Comment 17 Jesse Glick 2012-03-29 18:19:06 UTC
ccfe6270b994 changed labels but did not affect this behavior AFAIK; the bug was I think fixed earlier as part of the main project work.

*** This bug has been marked as a duplicate of bug 166780 ***