Biot Olivier wrote:
| From: Ulf Lamping
|
| Hi List!
|
| After thinking about this for a while now, I have doubts that
| the "From first to last marked packet" packet range option
| is really very intuitive to use, especially, as we have the user
| specified range option, which can do almost the same job.
This is true, but I tend to find it easier to mark packets in a
capture than to remember a range. Anyway, if entering a range,
the end-user has knowledge of this range, while with marking you
can focus on "Hey, that's an interesting packet" and then let
Ethereal grab the packets in that interval.
| As this might be comfortable in some (rare?) situations, it's very
| uncommon IMHO, so the novice user will have to think
| about this (and that's bad :-).
The novice user doesn't even know you can mark and unmark a packet.
| It's also becoming difficult to say, what will happen in some
| situations: e.g. when using a display filter,
| should the marked range start at the first marked packet, or
| the first *displayed* marked packet.
This is clear to me: the marked selection depends on the presence
or not of a display filter. When a display filter is active, then
the marked packet range only includes packets from this range that
*also* match the display filter. This is also true for the case
where the end-user manually specifies a packet range.
| I would like to remove this option completely, to clarify the user
| interface at this point.
I'm more in favor of adding either a brief tutorial to the Ethereal
distribution and to add a "Tip of the day" option which is enabled
by default.
| Someone really disagrees with this?
Should we rephrase the "range from 1st to last marked packet"
feature, document it or get rid of it? I'm in favor of keeping and
therefore documenting it.
Regards,
Olivier
Ok, ok, I leave it, like it is...
So I have to to some work now, as the displayed mark frame range has a
minor bug in it.
Regards, ULFL