Bug 75396 - [Intro] Intro page should go to "stand by" mode even if user selects already active perspective.
Summary: [Intro] Intro page should go to "stand by" mode even if user selects already ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-09-30 12:31 EDT by Ilya Rozenberg CLA
Modified: 2019-09-06 16:05 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Rozenberg CLA 2004-09-30 12:31:42 EDT
Our users did not realize (for some reason) to click on go to Workbench arrow 
to make intro (new welcome page) in "stand by" move. Instead they to switch to 
the perspective that is already open. Can we put some logic that would mode 
intro from full to stand by mode if user tries to switch to the already opened 
perspective?

There is already this logic when you switch to another perspective, so you need 
to move this code “up” a bit, before the check for perspective being already 
active.

Thanks
Comment 1 Ilya Rozenberg CLA 2004-09-30 12:36:20 EDT
Our users did not realize (for some reason) to click on ‘go to Workbench’ arrow 
to make intro (new welcome page) in ‘stand by’ mode.
Instead they try to switch to the perspective that is already open.

Can we put some logic that would move intro from full to stand by mode even if 
user tries to switch to the already opened perspective?

There is already this logic when you switch to another perspective, so you need 
to move this code “up” a bit, before the check for perspective being already 
active.
Comment 2 Susan McCourt CLA 2009-07-09 19:09:18 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:05:57 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.