Bug 61791 - Please allow a Tracker to be drawn without running its own event loop
Summary: Please allow a Tracker to be drawn without running its own event loop
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-11 16:01 EDT by Stefan Xenos CLA
Modified: 2019-09-06 03:34 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 Stefan Xenos CLA 2004-05-11 16:01:51 EDT
The Eclipse UI uses animated rectangles when minimizing fastviews and progress
dialogs. The current implementation only works on Windows. 

SWT has a useful Tracker class that draws exactly what is needed on all
platforms. However, the current implementation runs its own event loop whenever
a Tracker is being displayed.

The enhancement requests new API on the Tracker class so that it can be used for
these animations.


For example, it would be perfect if this were possible:

Tracker newTracker = new Tracker(myDisplay);
newTracker.setBounds(someRectangle);
newTracker.setVisible(true);

// Control continues here immediately... but now there is a Tracker 
// rectangle drawn in front of everything.
Comment 1 Stefan Xenos CLA 2004-05-11 16:10:12 EDT
Note: this bug would also be solved if there some other way to draw a rectangle
in front of everything that worked on all platforms.
Comment 2 Steve Northover CLA 2004-05-14 19:09:11 EDT
This sounds good to me but requires new API and we are API frozen for 3.0.  If 
this is important, please escalate with MVM.  Thanks.
Comment 3 Lars Vogel CLA 2019-09-06 03:34:37 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 and remove the stalebug whiteboard tag. 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.