Re: Problem with val_to_str inside BASE_CUSTOM callback function

[Thomas Wiens <th.wiens () gmx de>]

On 21.10.2016 22:49, Michael Mann wrote:
> Depending on what you're doing, you could go with
> proto_tree_add_xxx_format_value.   I think that's how most dissectors
> end up avoiding the need for BASE_CUSTOM callback.

Maybe one of you has another solution for what I want to realize.

In my protocol I've got an ID list with now ~1500 fixed values, where I
am using a value_string_ext list.
But there are dynamic list entries, for example all IDs between
0x92000000 and 0x92ffffff should be shown as DB.%d.%d using some masks.

-- 
Thomas


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe