Bug 151856 - [Presentations] Maximize functionality on tab click
Summary: [Presentations] Maximize functionality on tab click
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.2   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-07-26 10:51 EDT by Kazan CLA
Modified: 2019-09-06 16:12 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kazan CLA 2006-07-26 10:51:42 EDT 
I am trying to implement tab click functionality.  When the user clicks on a tab, the correpsonding view should be maximized.  Once the view is maximized, if the user clicks the tab, then the view should be restored to its original state.

This functionality is implemented in the Eclipse IDE, but as I understand it, this is not part of the API. 

Is this correct?

According to this post on eclipsezone.org, there is no built-in way to handle this:
http://www.eclipsezone.org/forums/thread.jspa?messageID=91889334&#91889334
Comment 1 Paul Webster CLA 2006-07-28 10:55:24 EDT 
You could provide this type of functionality if you write your own presentation.  Then you would be communicating with the IStackPresentationSite to request maximize and restore.

PW
Comment 2 Paul Webster CLA 2006-08-03 09:15:04 EDT 
Check out org.eclipse.ui.examples.presentation in the eclipse CVS repository.  It contains a couple of examples of writing a presentation, as well as EclipseCon slides.

For CVS information http://wiki.eclipse.org/index.php/CVS_Howto

PW
Comment 3 Paul Webster CLA 2006-09-28 11:01:52 EDT 
There are currently no plans to work on this feature.

PW
Comment 4 Denis Roy CLA 2007-06-22 09:33:30 EDT 
Changes requested on bug 193523
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:12:32 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.