diff options
| author | Jeff Morriss <jeff.morriss.ws@gmail.com> | 2016-07-17 18:24:45 -0400 |
|---|---|---|
| committer | Michael Mann <mmann78@netscape.net> | 2016-07-20 03:00:52 +0000 |
| commit | 29a98d1c7f09cba3a1e20ae6bfce76cf13e134fe (patch) | |
| tree | 6a7c5af0efefddbcb8beb45aeac793dd30d54059 /doc/README.dissector | |
| parent | 83174a207994c5d30c24e7907fffdc3644a52557 (diff) | |
Allow BASE_NONE (with strings conversion) for integral values again.
This mostly reverts SVN rev 43412 (3fa645481f82e32d5ad01ebce9c482c4edae31ae)
with the addition of documenting that FT_*INT*'s with BASE_NONE and a
FIELDCONVERT tells the Wireshark core that the field's numeric value is
meaningless and should not be shown to the user.
Use BASE_NONE again with the expert info group and severity fields. This
(finally) resolves the complaint from:
https://www.wireshark.org/lists/wireshark-dev/201206/msg00188.html
(yes, this mail's been sitting in my "todo" pile since then! <sigh>)
Change-Id: I1c6dd2864e7a2e959c97c409f277853af74a8d93
Reviewed-on: https://code.wireshark.org/review/16518
Petri-Dish: Jeff Morriss <jeff.morriss.ws@gmail.com>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Michael Mann <mmann78@netscape.net>
Diffstat (limited to 'doc/README.dissector')
| -rw-r--r-- | doc/README.dissector | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/README.dissector b/doc/README.dissector index 36367696ff..17b3273336 100644 --- a/doc/README.dissector +++ b/doc/README.dissector @@ -112,11 +112,18 @@ FIELDTYPE FT_NONE, FT_BOOLEAN, FT_UINT8, FT_UINT16, FT_UINT24, FT_IPv6, FT_IPXNET, FT_FRAMENUM, FT_PROTOCOL, FT_GUID, FT_OID, FT_REL_OID, FT_AX25, FT_VINES, FT_SYSTEM_ID, FT_FC, FT_FCWWN FIELDDISPLAY --For FT_UINT{8,16,24,32,40,48,56,64} and - FT_INT{8,16,24,32,40,48,56,64): + FT_INT{8,16,24,32,40,48,56,64): BASE_DEC, BASE_HEX, BASE_OCT, BASE_DEC_HEX, BASE_HEX_DEC, - or BASE_CUSTOM, possibly ORed with BASE_RANGE_STRING, - BASE_EXT_STRING or BASE_VAL64_STRING + BASE_CUSTOM, or BASE_NONE, possibly ORed with + BASE_RANGE_STRING, BASE_EXT_STRING or BASE_VAL64_STRING. + + BASE_NONE may be used with a non-NULL FIELDCONVERT when the + numeric value of the field itself is not of significance to + the user (for example, the number is a generated field). + When this is the case the numeric value is not shown to the + user in the protocol decode nor is it used when preparing + filters for the field in question. --For FT_UINT16: |