3.3 se_tree_insert_string / se_tree_lookup_string
-to be added...
+void emem_tree_insert_string(emem_tree_t* h, const gchar* k, void* v, guint32 flags);
+void* emem_tree_lookup_string(emem_tree_t* h, const gchar* k, guint32 flags);
+These functions are essentially wrappers for se_tree_insert32_array and
+se_tree_lookup32_array, tailered to text strings. They extend the text string
+into an array key and use that to key the se_tree_insert32_array and
+se_tree_lookup32_array functions.
+In order to support text string in a case insensitive way add the
+EMEM_TREE_STRING_NOCASE flag. This will uppercase all string data before using
+it as key data.
+
the header_field_info struct to see what information is expected:
struct header_field_info {
- char *name;
- char *abbrev;
+ const char *name;
+ const char *abbrev;
enum ftenum type;
int display;
- void *strings;
- guint bitmask;
- char *blurb;
-
- int id; /* calculated */
- int parent;
- int bitshift; /* calculated */
+ const void *strings;
+ guint32 bitmask;
+ const char *blurb;
+ .....
};
name
leave only the bits needed to make the field when ANDed with a value.
The proto_tree routines will calculate 'bitshift' automatically
from 'bitmask', by finding the rightmost set bit in the bitmask.
+This shift is applied before applying string mapping functions or
+filtering.
If the field is not a bitfield, then bitmask should be set to 0.
blurb
-----
-This is a string giving a proper description of the field.
-It should be at least one grammatically complete sentence.
+This is a string giving a proper description of the field. It should be
+at least one grammatically complete sentence, or NULL in which case the
+name field is used.
It is meant to provide a more detailed description of the field than the
name alone provides. This information will be used in the man page, and
in a future GUI display-filter creation tool. We might also add tooltips
- Edit the diff file - remove any changes unrelated to your new dissector,
e.g. changes in config.nmake
- - Send a note with the attached diff file requesting its inclusion to
- <mailto:wireshark-dev[AT]wireshark.org>. You can also use this procedure for
- providing patches to your dissector or any other part of Wireshark.
+ - Submit a bug report to the Wireshark bug database, found at
+ <http://bugs.wireshark.org>, qualified as an enhancement and attach your
+ diff file there. Set the review request flag to '?' so it will pop up in
+ the patch review list.
- Create a Wiki page on the protocol at <http://wiki.wireshark.org>.
A template is provided so it is easy to setup in a consistent style.
=item File Open Preview timeout
+This items allows the user to define how much time is spend reading the
+capture file to present preview data in the File Open dialog.
+
=item Open Recent maximum list entries
+The File menu supports a recent file list. This items allows the user to
+specify how many files are kept track of in this list.
+
=item Ask for unsaved capture files
+When closing a capture file or Wireshark itself if the file isn't saved yet
+the user is presented the option to save the file when this item is set.
+
=item Wrap during find
+This items determines the behaviour when reaching the beginning or the end
+of a capture file. When set the search wraps around and continues, otherwise
+it stops.
+
=item Settings dialogs show a save button
+This item determines if the various dialogs sport an explicit Save button
+or that save is implicit in Ok / Apply.
+
=item Web browser command
+This entry specifies the command line to launch a web browser. It is used
+to access online content, like the Wiki and user guide. Use '%s' to place
+the request URL in the command line.
+
=back
=item Layout Preferences