| Summary: | Restoring minimized view stack does not grant it focus if its active view was closed | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Remy Suen <remy.suen> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | yo0702suke |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Remy Suen
Not sure that this is a bug... in 4), using the context menu to close the view means that the Package Explorer remains the active part correct ? Given that the Package Explorer is the active part then why would restoring a different stack force the active part into that stack ? (In reply to comment #1) > in 4), using the context menu to close the view means that the Package Explorer > remains the active part correct ? Yes, during that operation, the 'Package Explorer' remains the active part. > Given that the Package Explorer is the active part then why would restoring a > different stack force the active part into that stack ? Because when performing steps 1 and 2. The 'Problems' view becomes the active stack even though the 'Package Explorer' was the active part. 1. Activate the 'Package Explorer'. 2. Minimize the stack with the 'Problems' view in it. Note that the 'Package Explorer' is still the active part. 3. Restore it. The 'Problems' view is now the active part. This is different from the scenario described in comment 0 where the active part stays as being the 'Package Explorer' and not a part in the stack that was restored from its minimized state. Does this make sense? 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. -- The automated Eclipse Genie. |