https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3810
Michael Mann <mmann78@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmann78@xxxxxxxxxxxx
--- Comment #3 from Michael Mann <mmann78@xxxxxxxxxxxx> 2011-07-07 13:00:12 PDT ---
(In reply to comment #1)
> In both cases, there was no delay at startup. The file was listed under the
> "Open Recent:" files, but grayed-out and marked as "[not found]".
If Wireshark can identify the file as "not found", it must have tried to look
for it. I assume Wireshark didn't mark it as "not found" only after you tried
to load it (I would expect it to be removed from the list at that point)
I've run into this problem with Windows completely independent of Wireshark
(having slow connections to mapped network drives slows a lot of my "context
sensitive" operations), but I don't understand why Wireshark looks for the file
in the first place. Shouldn't the Open Recent just be a static list of files
and Wireshark would only attempt to look for/open the file if selected? IMO it
shouldn't cache the file's availability.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
