Bug 55794 - [Workbench] Build Working Set should be disabled in autobuild mode
Summary: [Workbench] Build Working Set should be disabled in autobuild mode
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Michael Van Meekeren CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-23 17:52 EST by John Wiegand CLA
Modified: 2004-05-25 11:03 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Wiegand CLA 2004-03-23 17:52:06 EST
20040323

In autobuild mode, should gray out Build Working Set".  Currently build all is 
disabled, but build working set is not.  It took me > 30 seconds to figure out 
why.
Comment 1 John Arthorne CLA 2004-03-24 12:06:48 EST
I am happy to be convinced otherwise but this was actually deliberate.  A study
of the other sub-menus in the menu bar (Edit->Expand Selection, Edit->Encoding,
Source->Convert Line Delimeters, and all of the Search sub-menus), showed that
they all remain enabled even when all sub-menu items are disabled. Presumably
this aids user discovery by allowing them to see what is potentially available
in that menu. I imagine that greying the sub-menu entirely would still leave the
open question, "why is this menu disabled?" The approach in 2.1 was to remove
build actions from the menus entirely when autobuild was turned on.
Comment 2 John Arthorne CLA 2004-04-19 11:41:28 EDT
There doesn't even seem to be API to make a menu disabled.  I am going to close
this, since this goes against the convention followed in the platform.  I have
added a toggle action to enable/disable autobuild directly into the project
menu, so this should make it easier to figure out why the manual build actions
are disabled when autobuild is turned on.
Comment 3 John Arthorne CLA 2004-05-25 11:03:30 EDT
*** Bug 63826 has been marked as a duplicate of this bug. ***