I'm not sure that this is a bug because it's being reported by only one of fifteen users.
We are using the command-line version of our source control software (which is NOT integrated into Zeus) and we use LUA scripts to check-out and check-in source code files.
The scripts that perform the check-out and check-in functions call the NavigatorRefresh() function after performing the check-out or check-in. If the user has the 'Drives' tab is selected in the Navigator pane, the script hangs.
I can perform these operations without the hang on my computer so I'm wondering if there might be some configuration or drive mapping issue that might affect the performance of Zeus. It is possible that this one user has some drive mapping or configuration setting that is different from our other users.
Any thoughts, comments or suggestions are welcome.
TIA,
Jon
NavigatorRefresh hangs when 'Drives' tab is selected
Hi Jon,
Taking a look at the Zeus NavigatorRefresh code, this function does nothing more than use these Win32 functions to load the file tree:
As to why these functions should take a long time, I am not really sure, but suspect it could be network or drive mapping related. My guess is one of these functions is taking a long time to complete and this is resulting in the Zeus hang
I have witnesses situation where on occasions Zeus will hang for up to 5 to 10 seconds and from what I can tell, on these occasions Zeus was editing a file of a network drive.
In my case the Zeus hang is very much sporadic, impossible to replicate at will and given enough time Zeus always to normal operation. In some cases I have also noticed that closing the network file results in an immediate speed improvement in Zeus. For these reasons I put this hang down to Zeus waiting on the network drive to respond.
Cheers Jussi
Taking a look at the Zeus NavigatorRefresh code, this function does nothing more than use these Win32 functions to load the file tree:
- GetLogicalDrives
- FindFirstFile
- FindNextFile
As to why these functions should take a long time, I am not really sure, but suspect it could be network or drive mapping related. My guess is one of these functions is taking a long time to complete and this is resulting in the Zeus hang
I have witnesses situation where on occasions Zeus will hang for up to 5 to 10 seconds and from what I can tell, on these occasions Zeus was editing a file of a network drive.
In my case the Zeus hang is very much sporadic, impossible to replicate at will and given enough time Zeus always to normal operation. In some cases I have also noticed that closing the network file results in an immediate speed improvement in Zeus. For these reasons I put this hang down to Zeus waiting on the network drive to respond.
Cheers Jussi