Wireshark-dev: Re: [Wireshark-dev] New feature: custom columns
From: "Maynard, Chris" <[email protected]>
Date: Sun, 24 Feb 2008 18:23:16 -0500
I attached the patch in the last e-mail, entitled "column.patch".  Did it not go through?  Let me know if I should resend it.


From: [email protected] on behalf of Stephen Fisher
Sent: Sun 2/24/2008 5:34 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] New feature: custom columns

On Fri, Feb 22, 2008 at 09:49:39PM -0500, Maynard, Chris wrote:

> I would prefer to keep the custom columns for 0.99.8, even if not
> fully completed.  If it remains undocumented, then I doubt most people
> outside of those reading this list will even know it's there, and most
> people who do know it's there will be aware that there may be some
> deficiencies, but I think it's going to prove useful enough that it
> should remain.

Okay, we will leave them and hope no one finds it accidently and gets
hung up on it :).  They can always come here or to -users and ask for

> In a prior e-mail, I suggested alphabetizing the column choices.  The
> attached patch does just that.  Unfortunately, I had to run distclean
> after the changes; otherwise the columns are all messed up.  The patch
> involved re-ordering the dlist[] array in column.c so that the text
> was alphabetical, then re-ordering the slist[] array above it, as well
> as the enums in column_info.h to match.  To make it easier for myself,
> I numbered both dlist[] and slist[] (in comments) before I started,
> then re-arranged the dlist[].  Afterwards, I re-arranged slist[] so
> the now out-of-order numbers matched and finally did the same for the
> enums.  Finally, I re-numbered them all sequentially and added notes
> about trying to keep them alphabetized.

Interesting idea.  Do you have a patch handy for your work that we could
review for inclusion in the next version?


Wireshark-dev mailing list
[email protected]

This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.