Bug 98142 - [CTabFolder] Provide API to determine if a point is over a close button in CTabFolder
Summary: [CTabFolder] Provide API to determine if a point is over a close button in CT...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Duong Nguyen CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97969
  Show dependency tree
 
Reported: 2005-06-02 12:49 EDT by Stefan Xenos CLA
Modified: 2019-09-06 16:10 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Xenos CLA 2005-06-02 12:49:10 EDT
Please provide API to determine if a point is over a close button in CTabFolder.
This would be used to filter mouse events like double-click and mousedown, which
should have different behaviors when they fall on a close button.
Comment 1 Veronika Irvine CLA 2005-06-03 10:47:18 EDT
I strongly recommend against using low level events such as MouseDown and 
MouseDoubleCLick unless you are implementing a widget.

You should use events like Selection adn DEfaultSelection instead.  These 
events do not interfere with Close behaviour.
Comment 2 Stefan Xenos CLA 2005-06-03 14:25:54 EDT
That is reasonable, but in that case how can we implement the
double-click-to-maximize behavior?

There's also a good reason for the mousedown listener - I seem to recall it's
the only way to send focus to the view when the user clicks on a tab. (I tried
to remove it in the first cut of the 3.0 new look and it created regressions -
we can try again, though).

Please suggest alternatives.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:10:54 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.