Maynard, Chris wrote:
> One more thing, after alphabetizing the column choices in the last
> patch I submitted, it seems to me that there are quite a few
> redundancies. For example:
>
> 1) Hardware src addr <=> Hw src addr (resolved)
> 2) Hardware dest addr <=> Hw dest addr (resolved)
> 3) Sourc
On Sun, Feb 24, 2008 at 03:37:19PM -0700, Stephen Fisher wrote:
> On Fri, Feb 22, 2008 at 11:41:31PM +0100, Stig Bjørlykke wrote:
>
> > When having a custom column the "Apply as Filter" and "Prepare a
> > Filter" does not work as expected in the Packet List. Sometimes
> > nothing is selected,
On Fri, Feb 22, 2008 at 09:49:39PM -0500, Maynard, Chris wrote:
> In a prior e-mail, I suggested alphabetizing the column choices. The
> attached patch does just that.
I have commited your patch as SVN revision 24458. Thanks!
> Unfortunately, I had to run distclean after the changes; otherwis
ttle more obvious as to what that text entry box
is for.
From: [EMAIL PROTECTED] on behalf of Stig Bjørlykke
Sent: Sun 2/24/2008 7:41 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] New feature: custom columns
On 23. feb.. 2008, at 1
ubject: 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
On Fri, Feb 22, 2008 at 11:41:31PM +0100, Stig Bjørlykke wrote:
> When having a custom column the "Apply as Filter" and "Prepare a
> Filter" does not work as expected in the Packet List. Sometimes
> nothing is selected, sometimes "frame.number == 1" is added to the
> Filter and sometimes the s
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 k
On 23. feb.. 2008, at 15.20, Maynard, Chris wrote:
> BTW: I tested "eth.src" as a custom column, but it does not sort
> correctly. I know there's a column preference for it already, which
> does sort correctly though, so maybe it's no big deal?
Sorting custom columns according to field type
ROTECTED] On Behalf Of Stig Bjørlykke
Sent: Saturday, February 23, 2008 5:15 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] New feature: custom columns
2008/2/23, Maynard, Chris <[EMAIL PROTECTED]>:
> BTW: I added a new column, "Proto2" of type "
2008/2/23, Maynard, Chris <[EMAIL PROTECTED]>:
> BTW: I added a new column, "Proto2" of type "Protocol", so that there were
> now 2 of them. After hitting "OK", then going back into "Edit -> Preferences
> -> Columns", I saw this: "Proto2 Protocol ()". Note the empty parenthesis.
Yup, fixed i
the Custom column.
- Chris
1 attachment: column.patch: Contains a patch for 2 files, namely epan/column.c
and epan/column_info.h, which alphabetizes the column choices.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Fisher
Sent: Friday, February 2
On Fri, Feb 22, 2008 at 11:41:31PM +0100, Stig Bjørlykke wrote:
> When having a custom column the "Apply as Filter" and "Prepare a
> Filter" does not work as expected in the Packet List. Sometimes
> nothing is selected, sometimes "frame.number == 1" is added to the
> Filter and sometimes the s
Steve,
When having a custom column the "Apply as Filter" and "Prepare a
Filter" does not work as expected in the Packet List. Sometimes
nothing is selected, sometimes "frame.number == 1" is added to the
Filter and sometimes the selection is invalid. I haven't found a
pattern yet.
You sh
2008/2/22, Stig Bjørlykke <[EMAIL PROTECTED]>:
> 2008/2/12, Stephen Fisher <[EMAIL PROTECTED]>:
>
> > NOTE: There are many fields that are not implemented yet in
> > epan/proto.c.
>
>
> You should have a look at values using bitmask, they does not display
> the correct value in the list.
> And
2008/2/12, Stephen Fisher <[EMAIL PROTECTED]>:
> NOTE: There are many fields that are not implemented yet in
> epan/proto.c.
You should have a look at values using bitmask, they does not display
the correct value in the list.
And maybe have another default width for custom? The length of the
fi
On Mon, Feb 18, 2008 at 05:39:25PM -0700, Stephen Fisher wrote:
> On Sun, Feb 17, 2008 at 10:31:24AM -0500, Maynard, Chris wrote:
> > BTW, I added a column called, "ip.ttl", then tried to sort on that
> > column. It did not sort according to how I would expect. Rather than
> > sorting 1, 57, 5
Stephen Fisher wrote:
> On Mon, Feb 11, 2008 at 08:36:26PM -0700, Stephen Fisher wrote:
>
>> I have introduced a new feature [...] It lets you specify any display
>> filter name as a column by choosing the Custom column type and putting
>> the display filter name in the description.
>
> Gerald/
On Sun, Feb 17, 2008 at 10:31:24AM -0500, Maynard, Chris wrote:
> Nice feature. For me, the column naming convention wouldn't be a
> problem, but maybe it'd be nice to be able to name it something else,
> especially if the display filter name is long.
Good point about the long field names.
>
On Mon, Feb 11, 2008 at 08:36:26PM -0700, Stephen Fisher wrote:
> I have introduced a new feature [...] It lets you specify any display
> filter name as a column by choosing the Custom column type and putting
> the display filter name in the description.
Gerald/others - I just noticed that this
emove" column choices. Just a few ideas.
- Chris
From: [EMAIL PROTECTED] on behalf of Stephen Fisher
Sent: Mon 2/11/2008 10:36 PM
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] New feature: custom columns
I have introduced a new feature that I think people will re
I have introduced a new feature that I think people will really like
(and has been requested in one or two open bug reports.) It lets you
specify any display filter name as a column by choosing the Custom
column type and putting the display filter name in the description. For
example, go to p
21 matches
Mail list logo
