Bug 208238 - [GlobalActions] Unnecessary disabling of functions when side windows have focus
Summary: [GlobalActions] Unnecessary disabling of functions when side windows have focus
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-31 10:58 EDT by Chaise CLA
Modified: 2019-09-06 16:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chaise CLA 2007-10-31 10:58:48 EDT
Build ID: 3.3

Steps To Reproduce:
1. Open any project or source file.
2. Click on any visible sub-window other than the source window, such as the 'Project Explorer', 'Outline', or 'Problems' windows.
3. Note how certain toolbar buttons (along with their menu counterparts) become disabled unnecessarily, i.e. the 'Save', 'Print', 'Build', etc. functions are disabled when the window has focus.

More information:
There seems to be no discernible reasoning for why some functions are disabled when particular windows have focus. This is compounded by the fact that not all windows work uniformly, i.e. You can build the project when the 'Project Explorer' window has focus but not when the 'Make' window does.

This erratic behaviour is only confusing and can cause issues if someone attempts to save using the (Ctrl + S) shortcut when the 'Project Explorer' has focus and doesn’t realise the file has failed to save due to the function being temporarily disabled.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:09:11 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.