Re: [Wireshark-dev] About Custom Column

2009-09-09 Thread Sean
Thanks, Bug #3992 has been added. --- On Wed, 9/9/09, Kovarththanan Rajaratnam wrote: > From: Kovarththanan Rajaratnam > Subject: Re: [Wireshark-dev] About Custom Column > To: wireshark-dev@wireshark.org > Date: Wednesday, September 9, 2009, 12:15 PM > Hey Sean, > &g

Re: [Wireshark-dev] About Custom Column

2009-09-08 Thread Kovarththanan Rajaratnam
Hey Sean, Sean wrote: > Hi, > > I have updated several files to get this function work, > Would anyone check if it's acceptable to the community version? > or should I open a bug regarding this patch? Yes, please do that. > Please find the detail information for this function from the enclosed

Re: [Wireshark-dev] About Custom Column

2009-09-08 Thread Sean
24/09, didier wrote: > From: didier > Subject: Re: [Wireshark-dev] About Custom Column > To: "Developer support list for Wireshark" > Date: Monday, August 24, 2009, 9:23 PM > Le lundi 24 août 2009 à 15:05 > +0200, Stig Bjørlykke a écrit : > > On Mon, Aug 24, 2009 at 3

Re: [Wireshark-dev] About Custom Column

2009-08-24 Thread didier
Le lundi 24 août 2009 à 15:05 +0200, Stig Bjørlykke a écrit : > On Mon, Aug 24, 2009 at 3:00 PM, Sean wrote: > > Does anyone know is there anyway to add a column with several different > > fields? for example, by expression like: > > dissector1.field1 || dissector2.field2 > > This is not possib

Re: [Wireshark-dev] About Custom Column

2009-08-24 Thread Stig Bjørlykke
On Mon, Aug 24, 2009 at 3:00 PM, Sean wrote: > Does anyone know is there anyway to add a column with several different > fields? for example, by expression like: >   dissector1.field1 || dissector2.field2 This is not possible with the current implementation. -- Stig Bjørlykke _

[Wireshark-dev] About Custom Column

2009-08-24 Thread Sean
Hi, As I know, Wireshark supports custom column with user defined data field, Does anyone know is there anyway to add a column with several different fields? for example, by expression like: dissector1.field1 || dissector2.field2 That means, field1 will be shown on the column for dissector1 p