I do have a mapped network drive...can't remember if I was experiencing the same behavior before I mapped the drive. I'll check that out later today, and file a bug.
From: Greg Brown [mailto:[email protected]] Sent: Friday, March 05, 2010 8:44 AM To: [email protected] Subject: Re: Sluggish UI with the FileBrowserSheet OK, that's good. Do you have any mapped network drives by any chance? Might be relevant, might not. Best thing to do is probably file a bug. Include as much information as you can, and we'll see if we can track it down. On Mar 5, 2010, at 9:40 AM, David McNelis wrote: Sorry, 1.6.0_18 From: Greg Brown [mailto:[email protected]] Sent: Friday, March 05, 2010 8:38 AM To: [email protected] Subject: Re: Sluggish UI with the FileBrowserSheet Not sure it is relevant, but specifically which Java version are you using? For example (from running java -version at a command prompt): Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-10M3025) On Mar 5, 2010, at 9:35 AM, David McNelis wrote: Currently running XP, JRE 1.6, on the desktop at present. From: Greg Brown [mailto:[email protected]] Sent: Friday, March 05, 2010 8:33 AM To: [email protected] Subject: Re: Sluggish UI with the FileBrowserSheet I haven't seen any major issues with the file browser sheet myself, but it is certainly possible - it is a fairly complex component. What OS/JRE version are you using? Are you running in a browser or on the desktop? On Mar 5, 2010, at 9:20 AM, David McNelis wrote: I was wondering if this is a product of my environment, or something others have had issues with? For the most part the graphical elements I've dealt with are responsive, quick to paint, don't cause any issue. But I've notice a lot of inconsistency when opening a FileBrowserSheet. Sometimes it pops up immediately, the next time it might take several seconds. One time through it will move quickly through the directory structure, other times there is very noticeable lag between clicking and anything happening. I don't think its an issue with my implementation...but if someone thinks it might be, I can post an example from my application. This probably seems a minor thing to have a qualm with, but I've found myself double clicking a directory and because there is no response from the UI other than to highlight the directory, I end up clicking again...opening whatever file my cursor happens to be over when I double click the second time. If I'm doing this and KNOW what my app is doing, I can see end users getting easily frustrated. Any thoughts?
