I've seen similar behavior on Windows when people have software added that interacts with the Explorer directly, like the Gmail Drive Shell Extension. This class of software can be considered shell extensions.
Ironically, when I use Adobe Lightroom, it exhibits similar behavior for me. If I remember correctly, when the native browse windows comes up, the Gmail extension prompts me to log into the drive. But I imagine any similar Shell extension could potentially cause the browse dialog box to hang while Explorer resolves things. There could be some quirks if the user had a cd/dvd in the drive, etc... I know it's not a direct answer, but it could help you down the path of discovery. --- In [email protected], "thirtyfivemph" <[EMAIL PROTECTED]> wrote: > > I don't ever have this problem on my machine (MacBookPro, OSX), but my > partner has it quite often on his (Dell laptop, WindowsXP): > > In our app, we call FileReference.browse for the user to select a > local file. I've got a that call as basically the only code in the > click event handler for a button. On my partner's machine, he clicks > the button and sometimes has to wait a minute or more before the OS > open dialog shows up. > > I'm not sure what I could be doing to affect the amount of time it > takes for the OS dialog to show, and it may just be a quirk of his > machine. Is there any way I can fix this, or if not, handle it gracefully? > > Troy. >
