[
https://issues.apache.org/jira/browse/PIVOT-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161549#comment-13161549
]
Sandro Martini commented on PIVOT-656:
--------------------------------------
Hi, thank you very much for all the work.
I'll test the new patch and commit today so others can make some other test
just before freezing 2.0.1 final.
> I tested on the FileBrowsing example from the tutorial (because my
> application has little problems with 2.0.1) .
I hope they are problems not caused by Pivot 2.0.1, otherwise please tell us.
> Everything seems to be fine but shoud of course be tested by somebody else.
After the commit I'll mark this issue as resolved, please reopen it (asap) in
case of problems.
Thank you again,
Sandro
> 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
>
> Attachments:
> apache-pivot-terra-fileBrowserSkin-performance-trunk.patch,
> apache-pivot-terra-fileBrowserSkin-performance.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
