Summary: | [WorkbenchParts] PageBook Control needs a getPage() method | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Timothy Halloran <hallorant> | ||||
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | ppshah, pwebster, remy.suen | ||||
Version: | 3.3 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Timothy Halloran
2007-09-24 09:11:45 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." Another related problem: PageBook#setFocus() sets the focus to the first focusable child; it should set it on the current page instead. Updated as per http://wiki.eclipse.org/Platform_UI/Bug_Triage PW 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. |