https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4014
--- Comment #11 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2010-06-16 11:50:58 PDT ---
Sure the fields can all be added as custom columns, but do you really want to
necessarily do that? I mean the same could be said for all the the information
contained on a TCP information column, couldn't it? The idea was to simply
present the same type of information that is normally displayed using a utility
such as ping w/out having to add extra custom columns.
Define "messy"? If you mean the seq # being displayed in both big- and
little-endian format, then I somewhat agree. I wish it were possible to
reliably determine the byte ordering and only display the applicable one, but I
wasn't able to come up with such a method. Displaying both allows you to
easily tell which byte ordering is used and to be able to follow the sequencing
to tell if there are dropped requests and/or replies and when they occurred.
On the other hand, if you mean all of the extra information, then I disagree.
Well, I personally don't view the extra information as messy or see any
benefit/need to ever turning it off. I also think disabling it by default
means that most users won't ever see it because they won't think to go to the
ICMP preferences to enable it. But if it bothers you that much, then I guess
go ahead and add some preference to disable it or otherwise make whatever
changes you need so it's more to your liking even if it means reverting the
patch altogether. I can cope. :)
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
