Re: 'Virtual' subtree

[Simon Zhong <szhong.jnpr () gmail com>]

Thanks guys, I will give it a try.

On Tue, Sep 30, 2014 at 1:03 PM, <mmann78 () netscape net> wrote:

> You can group fields in whatever way makes sense for your protocol, it
> doesn't always have to be flat or a "real" field (or a "real" structure).
> I would think that you would just call proto_tree_add_subtree() and pass it
> the title of <svec-list> or <request-list>.  You may have to call
> proto_item_set_len later on the proto_item* populated by
> proto_tree_add_subtree() so that the bytes are correctly highlighted.
>
>
>
> -----Original Message-----
> From: Simon Zhong <szhong.jnpr () gmail com>
> To: wireshark-dev <wireshark-dev () wireshark org>
> Sent: Tue, Sep 30, 2014 8:59 am
> Subject: [Wireshark-dev] 'Virtual' subtree
>
>  Hi,
> I'm working on PCEP dissector, I'm wonder if it's possible to create a
> 'virtual' subtree.
> The format of a message is as follows:
> <PCReq Message>::= <Common Header>
>                   [<svec-list>]
>                   <request-list>
> where: <svec-list>::=<SVEC>[<svec-list>]
>       <request-list>::=<request>[<request-list>]
>       <request>::= <RP>
>                    <END-POINTS>
>                    [<LSPA>]
>                    [<BANDWIDTH>]
>                    [<metric-list>]
>                    [<RRO>[<BANDWIDTH>]]
>                    [<IRO>]
>                    [<LOAD-BALANCING>]
> ...
> As you can see there's no real field called <svec-list> or <request-list>,
> it's just set of some other real fields. But I believe it will be more
> clear if we can present these real fields under a 'virtual' subtree,
> instead of presenting them flatly.
> Is there any way to do this? Thanks.
> /Simon
>
>   ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org?subject=unsubscribe <wireshark-dev-request () wireshark 
> org?subject=unsubscribe>
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe