Bug 97969 - [Presentations] [ViewMgmt] Quickly closing two views is interpreted as double-click
Summary: [Presentations] [ViewMgmt] Quickly closing two views is interpreted as double...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 98142
Blocks:
  Show dependency tree
 
Reported: 2005-06-01 15:27 EDT by Boris Bokowski CLA
Modified: 2019-09-06 16:13 EDT (History)
0 users

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 Boris Bokowski CLA 2005-06-01 15:27:39 EDT 
In a tab group with multiple views, if you click the 'x' (close button) of two 
views quickly enough and without moving the mouse, you maximize the tab group 
because the two mouse clicks are interpreted as a double-click.

An easy way to reproduce is to start the RCP browser example, open the history 
view, type Ctrl-T a couple times to open many browser views until you see the 
chevron button and then try and close two browser views quickly.

This confused me quite a bit when it first happened.
Comment 1 Stefan Xenos CLA 2005-06-02 12:43:52 EDT 
Filtering out double-clicks over the close button would require API to determine
the location of the close button.
Comment 2 Stefan Xenos CLA 2005-06-02 12:50:02 EDT 
Filed bug 98142 requesting the new SWT api.
Comment 3 Boris Bokowski CLA 2009-11-11 17:30:41 EST 
Remy is now responsible for watching the [ViewMgmt] category.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:11 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.