Comment # 2
on bug 7545
from Guy Harris
(In reply to comment #1)
> Yes, this functionality was moved to the File->Export Specified Packets menu
> item. (There's more history to be read about why which I won't try to
> summarize here.)
For those who are curious:
The original "Save As" implementation combined two *different* operations:
1) "I have some unsaved data, please save it all as the file XXX and make
XXX the current file";
2) "I have a bunch of packets, let me write out some or all of them to
another file, but don't make the result the current file".
The difference between 1) and 2) was whether the operation saved all the
packets or not.
This was a bit of a hack. It wasn't *too* obvious prior to 1.8, as "unsaved
data" only meant "a live capture that hadn't been saved yet", but, in 1.8,
where you can edit a saved capture or a capture you've read in, because you can
add comments to, remove comments from, or edit comments on a packet, it became
a bit more obviously unlike other "editors".
I think least one bug was filed on that behavior during 1.7 development.
As of 1.8, 1) and 2) have been split into two separate operations. 1) is
"Save" and "Save As"; 2) is "Export Specified Packets".
This causes some disruption to people used to the pre-1.8 behavior, but it's
the New Normal; current and future Wireshark versions will continue the model
where "Save" and "Save As" will always write out all the packets and will
always make the "saved to" file the current file, and "Export Specified
Packets" will let you specify which packets to write and will not make the
"written to" file the current file.
You are receiving this mail because:
- You are watching all bug changes.