Hi,
From a code point of view (epan/proto.c) I can see why this is
happening. From a API point of view this looks wrong. If I'm serving the
function the value to work with I expect it to work with that value, not
its own interpretation of it.
Let's have a look at what happens if we change this
Hi all,
I have the following question: in the dissector I am writing, there is a
bitfield occupying bits [2..7] of a byte. I have defined it as follows:
{ &hf_x, { "X", "p.x", FT_UINT8, BASE_HEX, NULL, 0xfc, "", HFILL }}
Everything is okay if I add that field using proto_tree_add_item().
Howev
