Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355789 - SWT FileDialog will run slow on vista if you click on favorite link.
Summary: SWT FileDialog will run slow on vista if you click on favorite link.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows Vista
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-25 01:08 EDT by jf_malski CLA
Modified: 2019-11-14 03:39 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jf_malski CLA 2011-08-25 01:08:10 EDT
Build Identifier: Eclipse Helios 3.6.1

I'm using Windows Vista Home Premium 32bit, Eclipse Helios version 3.6.1, Java SE6, SWT. SWT FileDialog will run slow on vista if you click on favorite link. If you move the mouse away from the dialog and it's parent window it will automatically refresh the dialog box.  But if you don't move away the mouse from the dialog box and it's parent window it will take time to refresh the dialog.  This only happens if you click the Favorite Link, but the normal folder browsers work just fine.  This should be fix because user will think that Java or Eclipse or SWT is crappy.  I love these technologies and more users will be happy if this is fix :) Please help.  Thanks a lot guys!

Reproducible: Always

Steps to Reproduce:
1.) Create a windowed program in java using SWT and create the SWT's FileDialog (it doesn't matter if you used new FileDialog(shell, SWT.OPEN) or etc. 
2.) Launch the program then as soon as the FileDialog opens, click on the Favorite Link on the dialog box and you will see the issue.
Comment 1 Lars Vogel CLA 2019-11-14 03:39:40 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.