JFileChooser is slow to figure out that mapped drives are no longer available

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 1.1.6
    • Component/s: client-libs



      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)
      ======================================================================

            Assignee:
            Leif Samuelsson (Inactive)
            Reporter:
            Kevin Ryan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: