From 13964595ad09e5d1115f6c5cb604cded27f9f55d Mon Sep 17 00:00:00 2001 From: Michael Mann Date: Fri, 30 Dec 2016 12:26:34 -0500 Subject: Add BASE_NO_DISPLAY_VALUE to allow field value to not be shown. There are times when byte arrays don't want to show their value in the packet tree or there is a field that is the "header" of a subtree where showing the field value distracts from the tree display. For these cases, BASE_NO_DISPLAY_VALUE can be used to not display the value. Change-Id: I8c9f1f57cd2e663dbee07e2289e7f5e1f22d1e32 Reviewed-on: https://code.wireshark.org/review/19479 Reviewed-by: Michael Mann --- doc/README.dissector | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/README.dissector b/doc/README.dissector index a3ae632e22..911fd78889 100644 --- a/doc/README.dissector +++ b/doc/README.dissector @@ -117,7 +117,7 @@ FIELDDISPLAY --For FT_UINT{8,16,24,32,40,48,56,64} and BASE_DEC, BASE_HEX, BASE_OCT, BASE_DEC_HEX, BASE_HEX_DEC, BASE_CUSTOM, or BASE_NONE, possibly ORed with BASE_RANGE_STRING, BASE_EXT_STRING, BASE_VAL64_STRING, - BASE_ALLOW_ZERO or BASE_UNIT_STRING + BASE_ALLOW_ZERO, BASE_UNIT_STRING or BASE_NO_DISPLAY_VALUE BASE_NONE may be used with a non-NULL FIELDCONVERT when the numeric value of the field itself is not of significance to @@ -126,6 +126,11 @@ FIELDDISPLAY --For FT_UINT{8,16,24,32,40,48,56,64} and user in the protocol decode nor is it used when preparing filters for the field in question. + BASE_NO_DISPLAY_VALUE will just display the field name with + no value. It is intended for byte arrays (FT_BYTES) or + header fields above a subtree. The value will still be + filterable, just not displayed. + --For FT_UINT16: BASE_PT_UDP, BASE_PT_TCP, BASE_PT_DCCP or BASE_PT_SCTP -- cgit v1.2.1