https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4055
--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx> 2012-05-21 21:23:54 PDT ---
I've checked in a change to have similar capture file callbacks for reading a
file and reloading a file; this means the UI behaves similarly for a read and
reload, except that it says "Reloading" rather than "Loading".
Given that, as part of the reload process, the currently-open file is closed,
so the welcome screen shows up, and then while the reload is being done the
packet list is blank, the UI already makes the save process look a bit weird,
so I'm not sure having "Saving" in the progress dialog and status bar makes a
big difference. If it does, we could put it there.
The *real* problem is that we're doing the reload in the first place; not only
does that make the UI look funny, it also means some information *not* saved
with the file (marked frames, etc.) might get lost, and means that saving takes
longer than it really should. With some infrastructure changes, we should be
able to eliminate the reload.
--
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.