aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>2007-01-10 07:47:00 +0000
committerjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>2007-01-10 07:47:00 +0000
commitc006498e67d56765e9975268e2641401aeffdf11 (patch)
treee550ae0b45a1ca1d859b726bc2fe73294f353d9b /doc
parent0edbc33e8bc8237ff906ab3117773ff659f8f58b (diff)
Extending true_false_string support
- Separate tfs.[ch] - Add larger sample collection - Properly export DATA git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@20373 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'doc')
-rw-r--r--doc/README.developer5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/README.developer b/doc/README.developer
index 1aaa5a38d0..6d603f968e 100644
--- a/doc/README.developer
+++ b/doc/README.developer
@@ -1594,7 +1594,7 @@ behavior collapses to the one of value_string.
FT_BOOLEANS have a default map of 0 = "False", 1 (or anything else) = "True".
Sometimes it is useful to change the labels for boolean values (e.g.,
to "Yes"/"No", "Fast"/"Slow", etc.). For these mappings, a struct called
-true_false_string is used. (This struct is new as of Wireshark 0.7.6).
+true_false_string is used.
typedef struct true_false_string {
char *true_string;
@@ -1617,6 +1617,9 @@ string representing falsehood. For FT_BOOLEAN fields that need a
If the Boolean field is to be displayed as "False" or "True", the
'strings' field would be set to NULL.
+Wireshark predefines a whole range of ready made "true_false_string"s
+in tfs.h, included via packet.h.
+
bitmask
-------
If the field is a bitfield, then the bitmask is the mask which will