Den 7. sep. 2007 kl. 21.48 skrev Guy Harris:
It would require that a given protocol tree entry be able to have more
than one offset and length associated with it. That would probably be
useful in other places.
I suppose one extra set of start/length would be a good start. Maybe
calling it appendix, and having a proto_tree_set_appendix(tree, tvb,
offset, length) to add the data.
But which data should the Copy functions copy? The main data or both?
And the "Export Selected Bytes..."?
Created this bug report to propose an enhancement:
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1831
--
Stig Bjørlykke
