JDK-4247323 : JFileChooser is slow to figure out that mapped drives are no longer available
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.1.6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_nt
  • CPU: x86
  • Submitted: 1999-06-17
  • Updated: 2002-04-23
  • Resolved: 2002-04-23
Related Reports
Duplicate :  

Name: krT82822			Date: 06/17/99

[Not clear that there's any way, in win32, to find out -- in advance -- whether a drive is still available.  Thus, filing this as an RFE  --kevin.ryan@eng]

orig synopsis:  "JFileChooser takes a long time to come up"

JFileChhoser takes a long time to come up if any machine is mapped
from the current machine where the code is running and is
shut down at that time of bringing up the File Dialog 

It takes min of 1-2 minutes
(Review ID: 84474) 

WORK AROUND Name: krT82822 Date: 06/17/99 i coudnt find a work around for this , ======================================================================

EVALUATION This would be nice to fix. There might be a way to spin up a separate thread for hitting each drive (I believe that doing the f.isDirectory() is probably what's causing this). If it takes a long time, it can time out and the file chooser can merrily be on its way. jeff.dinkins@Eng 2000-03-09