Wireshark-bugs: [Wireshark-bugs] [Bug 6640] after fix for Bug 3046, after save-as then open you
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6640
--- Comment #1 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-12-02 08:42:29 PST ---
I'm not so sure that this bug has anything to do with the fix for bug3046. In
my testing on Windows XP (x86) top-of-trunk-1.6 (40068), I found that there is
no difference in behavior with or without the patch applied, and I don't get
the "File -> Closing!" hang in either case.
My results w/trunk-1.6 is that after you confirm to overwrite an existing file,
the current file appears to be closed so that no packets are displayed, but the
titlebar indicates the name of the newly overwritten file and the 'File ->
Close' is sensitive, so presumably the intent was for the current file to be
closed and the newly overwritten file to be created and loaded; however, that
doesn't happen.
The behavior with the SVN trunk is different though. In this case, the file is
overwritten, but the current file remains open and displayed. If you want to
view the new file, you have to manually open it as a separate step.
So ... we may have 2 bugs here, depending on the desired/expected behavior of
'File -> Save As'. If the intent is for the current file to be closed and the
new file to be created and opened, then there's a bug in the trunk as well as
the bug with not displaying the packets in trunk-1.6. So my question is, "What
is the desired/expected behavior of 'File -> Save As' in this regard?"
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
