[
https://issues.apache.org/jira/browse/PIVOT-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071665#comment-13071665
]
Chris Bartlett commented on PIVOT-656:
--------------------------------------
I wrote a custom DirectoryChooser component which shows the file system roots
as a tree and retains a MRU list (most recently used) of chosen directories
among other things.
The cleanest solution I came up with was to record the time taken to enumerate
the drives/mount points and special directories, and then store a flag in the
application preferences to identify the ones that loaded slowly. The next time
the DirectoryChooser is used, those slow nodes would be populated on separate
threads, but could just as easily lazy loaded when/if they were accessed
> FileBrowserSheet seems frozen while browsing network folders
> ------------------------------------------------------------
>
> Key: PIVOT-656
> URL: https://issues.apache.org/jira/browse/PIVOT-656
> Project: Pivot
> Issue Type: Improvement
> Affects Versions: 1.5.1
> Reporter: A.J.
> Fix For: 2.1
>
>
> Our customer complains about the FileBrowserSheet being unresponsive while
> browsing network folders.
> I haven't been able to reproduce this in my development environment but I saw
> this in 'action' (or inaction in this case).
> They click a folder then ... nothing happens, they wait, then wait. They are
> free to try other folders (I guess this is asynchronous task) but nothing
> happens.
> I've asked them to navigate the same network path with the Windows explorer
> which has no apparent problem (some slowdowns at worst).
> So, it's hard to say where the problems is (no stack trace) but there is a
> problem.
> One first improvement that could be done would be to display an hourglass
> (busy cursor) while the current I/O operation is pending.
> Another one could be also to set a timer after which the I/O operation would
> be canceled (or abandonned) and give back hand to the calling code.
> That's all I'm thinking fo r now.
> As soon as I can get some more info on the origin of the problem, I'll update
> this issue.
> Cheers,
> A.J.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
