pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandro Martini (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIVOT-656) FileBrowserSheet seems frozen while browsing network folders
Date Fri, 09 Dec 2011 23:30:40 GMT

    [ https://issues.apache.org/jira/browse/PIVOT-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166665#comment-13166665

Sandro Martini commented on PIVOT-656:

Hi Roger, yes I'm sure that the resize problem is not related to your fix, so it will be fixed
in a dedicated issue, but later.

> 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.
>            Assignee: Sandro Martini
>             Fix For: 2.0.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
> 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


View raw message