Add a preferences page for the name resolution flags.

Separate the preferences value for those flags and the name resolution
code's value into separate variables; this means that the resolution
code no longer depends on the preferences code, and may let us
eventually have the current setting and the preference setting differ
(so that a user can temporarily override the preference setting without
causing subsequent saves of the preferences to save the temporary
value).

Add routines to create various types of widgets for preferences, and to
fetch the values for "enumerated" preferences, and use them both in the
code to handle hardwired preference pages and table-driven preference
pages.

svn path=/trunk/; revision=4536

1 files changed, 1 insertions, 10 deletions

diff --git a/prefs.h b/prefs.h
index a6eccc3de6..e0c5a8c222 100644
--- a/prefs.h
+++ b/prefs.h
@@ -1,7 +1,7 @@
 /* prefs.h
  * Definitions for preference handling routines
  *
- * $Id: prefs.h,v 1.36 2002/01/10 07:43:37 guy Exp $
+ * $Id: prefs.h,v 1.37 2002/01/13 20:35:08 guy Exp $
  *
  * Ethereal - Network traffic analyzer
  * By Gerald Combs <gerald@ethereal.com>
@@ -35,15 +35,6 @@
 #define DEF_WIDTH 750
 #define DEF_HEIGHT 550
 
-/* 32 types are sufficient (as are 640k of RAM) */
-/* FIXME: Maybe MANUF/m, IP/i, IP6/6, IPX/x, UDP+TCP/t etc would be
-   more useful/consistent */
-#define PREFS_RESOLV_NONE	0x0
-#define PREFS_RESOLV_MAC	0x1
-#define PREFS_RESOLV_NETWORK	0x2
-#define PREFS_RESOLV_TRANSPORT	0x4
-#define PREFS_RESOLV_ALL	0xFFFFFFFF
-
 /*
  * Convert a string listing name resolution types to a bitmask of
  * those types.