Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 67561 - [ViewMgmt] Problems detaching fast view
Summary: [ViewMgmt] Problems detaching fast view
Status: RESOLVED DUPLICATE of bug 55536
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Stefan Xenos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-16 20:14 EDT by Nick Edgar CLA
Modified: 2004-10-26 12:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2004-06-16 20:14:30 EDT
RC2

- open a fast view 
- drag its tab out of the main window to be a detached view
- the drag rectangle gets stuck and stops following the mouse
- releasing the mouse button does not stop the drag
- clicking ends it

Workaround: drag the minimized fast view icon instead
Comment 1 Michael Van Meekeren CLA 2004-06-17 08:54:05 EDT
Grant have there been any changes in drag and drop in SWT recently? Nick, any 
exception or error in the log?
Comment 2 Nick Edgar CLA 2004-06-17 10:26:20 EDT
No, nothing in the .log.
Comment 3 Michael Van Meekeren CLA 2004-07-12 12:02:46 EDT
does this still happen Nick?
Comment 4 Nick Edgar CLA 2004-07-19 14:40:48 EDT
Looks like this was fixed in 3.0.
Comment 5 Stefan Xenos CLA 2004-07-20 02:39:21 EDT
This is not fixed in 3.0. In order to reproduce, you need to drag from the
fastview pane, not the fast view icon.

This is being caused by the fact that we dispose the fast view presentation
widgets after the mousedown. Can probably fix this by hiding the widgets rather
than disposing them.
Comment 6 Nick Edgar CLA 2004-07-20 11:13:42 EDT
Sorry, I goofed yesterday - I was detaching a regular view, not a fast view.
As you say, the problem is still there.
Comment 7 Stefan Xenos CLA 2004-10-26 12:04:02 EDT

*** This bug has been marked as a duplicate of 55536 ***