Bug 204441 - [WorkbenchParts] PageBook Control needs a getPage() method
Summary: [WorkbenchParts] PageBook Control needs a getPage() method
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 09:11 EDT by Timothy Halloran CLA
Modified: 2019-09-06 15:36 EDT (History)
3 users (show)

See Also:


Attachments
The PageBook code with proposed enhancements (3.70 KB, text/plain)
2007-09-24 09:11 EDT, Timothy Halloran CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Halloran CLA 2007-09-24 09:11:45 EDT
Created attachment 79071 [details]
The PageBook code with proposed enhancements

Build ID: 3.3

Steps To Reproduce:
The PageBook control remembers the current page that it is showing, however, client code doesn't have access to this.


More information:
I've implemented the method and also added Javadoc to fix bug 127308 as well.  I tried to avoid changing indentation, however the package is commented out so I could test the code.
Comment 1 Pratik Shah CLA 2007-10-15 15:00:10 EDT
A possible workaround would be to see which of the PageBook's children is visible.  However, that doesn't always work since the PageBook doesn't actually set all the pages to not be visible.  So, this would only work after each of the pages of the pagebook has been shown once.  Perhaps the javadoc should be fixed so that it doesn't say "only a single control is visible at a time."
Comment 2 Pratik Shah CLA 2007-10-15 15:03:33 EDT
Another related problem: PageBook#setFocus() sets the focus to the first focusable child; it should set it on the current page instead.
Comment 3 Paul Webster CLA 2009-03-02 11:41:27 EST
Updated as per http://wiki.eclipse.org/Platform_UI/Bug_Triage
PW
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:36:28 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.