Bug 67548 - [CTabFolder] API in CTabFolder and CTabItem to locate chrveron, close and min/max buttons
Summary: [CTabFolder] API in CTabFolder and CTabItem to locate chrveron, close and min...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Duong Nguyen CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-16 17:37 EDT by Xiangyan Zhong CLA
Modified: 2019-09-06 16:07 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xiangyan Zhong CLA 2004-06-16 17:37:50 EDT
In CTabFolder, there are three new areas Chevron, Maximize, Minimize. In M8, 
the rectangles are accessible through the following public methods: 
getChevronBounds, getMaximizeBounds, getMinimizeBounds. 
In CTabItem, there is a Close area. In M8, the rectangle is accessible through 
public method getCloseBounds. 

In M9, all those methods are missing. 

Those areas are not objects so the only way to get the rectangles are from 
CTabFolder and CTabItem methods. 

To support GUI Testing for Eclipse platform, those methods are critical. We 
need to make changes in our proxy code to support the changes in Eclipse3.0. It 
would be very helpful if the methods back there ASAP.
Comment 1 Veronika Irvine CLA 2004-06-17 09:33:12 EDT
This API was not required by Eclipse and was removed.  API was marked as under 
construction and subject to change.  The API will not be added for 3.0.

Changing this bug report to an enhancement request for post 3.0 consideration

Comment 2 Eclipse Webmaster CLA 2019-09-06 16:07:43 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.