1999-12-16 06:20:18 +00:00
|
|
|
/* gui_prefs.c
|
|
|
|
|
* Dialog box for GUI preferences
|
|
|
|
|
*
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
* $Id: gui_prefs.c,v 1.6 2000/08/20 07:53:43 guy Exp $
|
1999-12-16 06:20:18 +00:00
|
|
|
*
|
|
|
|
|
* Ethereal - Network traffic analyzer
|
|
|
|
|
* By Gerald Combs <gerald@zing.org>
|
|
|
|
|
* Copyright 1998 Gerald Combs
|
|
|
|
|
*
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
|
* as published by the Free Software Foundation; either version 2
|
|
|
|
|
* of the License, or (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
|
#include "config.h"
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#include <errno.h>
|
|
|
|
|
|
|
|
|
|
#include "globals.h"
|
|
|
|
|
#include "gui_prefs.h"
|
|
|
|
|
#include "gtkglobals.h"
|
|
|
|
|
#include "prefs_dlg.h"
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
#include "ui_util.h"
|
|
|
|
|
#include "dlg_utils.h"
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
static void scrollbar_menu_item_cb(GtkWidget *w, gpointer data);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
static void plist_sel_browse_cb(GtkWidget *w, gpointer data);
|
|
|
|
|
static void ptree_sel_browse_cb(GtkWidget *w, gpointer data);
|
1999-12-30 23:02:56 +00:00
|
|
|
static void ptree_line_style_cb(GtkWidget *w, gpointer data);
|
|
|
|
|
static void ptree_expander_style_cb(GtkWidget *w, gpointer data);
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
static void font_browse_cb(GtkWidget *w, gpointer data);
|
|
|
|
|
static void font_browse_ok_cb(GtkWidget *w, GtkFontSelectionDialog *fs);
|
|
|
|
|
static void font_browse_destroy(GtkWidget *win, gpointer data);
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
static gboolean temp_gui_scrollbar_on_right;
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
static gboolean temp_gui_plist_sel_browse;
|
|
|
|
|
static gboolean temp_gui_ptree_sel_browse;
|
1999-12-30 23:02:56 +00:00
|
|
|
static gint temp_gui_ptree_line_style;
|
|
|
|
|
static gint temp_gui_ptree_expander_style;
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
static gchar *temp_gui_font_name;
|
|
|
|
|
|
|
|
|
|
#define E_FONT_DIALOG_PTR_KEY "font_dialog_ptr"
|
|
|
|
|
#define E_FONT_CALLER_PTR_KEY "font_caller_ptr"
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
GtkWidget*
|
|
|
|
|
gui_prefs_show(void)
|
|
|
|
|
{
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
GtkWidget *main_tb, *main_vb, *label;
|
1999-12-30 23:02:56 +00:00
|
|
|
GtkWidget *menu_item_false, *menu_item_true,
|
|
|
|
|
*menu_item_0, *menu_item_1, *menu_item_2, *menu_item_3,
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
*scrollbar_menu, *scrollbar_option_menu, *font_bt;
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
temp_gui_scrollbar_on_right = prefs.gui_scrollbar_on_right;
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
temp_gui_plist_sel_browse = prefs.gui_plist_sel_browse;
|
|
|
|
|
temp_gui_ptree_sel_browse = prefs.gui_ptree_sel_browse;
|
1999-12-30 23:02:56 +00:00
|
|
|
temp_gui_ptree_line_style = prefs.gui_ptree_line_style;
|
|
|
|
|
temp_gui_ptree_expander_style = prefs.gui_ptree_expander_style;
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
temp_gui_font_name = g_strdup(prefs.gui_font_name);
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
/* Main vertical box */
|
|
|
|
|
main_vb = gtk_vbox_new(FALSE, 5);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
gtk_container_border_width( GTK_CONTAINER(main_vb), 5 );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
/* Main table */
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
main_tb = gtk_table_new(6, 2, FALSE);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
gtk_box_pack_start( GTK_BOX(main_vb), main_tb, FALSE, FALSE, 0 );
|
|
|
|
|
gtk_table_set_row_spacings( GTK_TABLE(main_tb), 10 );
|
|
|
|
|
gtk_table_set_col_spacings( GTK_TABLE(main_tb), 15 );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
/* Scrollbar placment */
|
1999-12-16 06:20:18 +00:00
|
|
|
label = gtk_label_new("Vertical Scrollbar Placement:");
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
gtk_misc_set_alignment( GTK_MISC(label), 1.0, 0.5 );
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), label, 0, 1, 0, 1 );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
/* Create a simple menu containing the LEFT/RIGHT choices for
|
|
|
|
|
* the scrollbar placement option */
|
|
|
|
|
scrollbar_menu = gtk_menu_new();
|
1999-12-30 23:02:56 +00:00
|
|
|
menu_item_false = gtk_menu_item_new_with_label("Left");
|
|
|
|
|
menu_item_true = gtk_menu_item_new_with_label("Right");
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_false );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_true );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_false), "activate",
|
1999-12-16 06:20:18 +00:00
|
|
|
scrollbar_menu_item_cb, GINT_TO_POINTER(FALSE) );
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_true), "activate",
|
1999-12-16 06:20:18 +00:00
|
|
|
scrollbar_menu_item_cb, GINT_TO_POINTER(TRUE) );
|
|
|
|
|
|
|
|
|
|
/* Create the option menu from the option */
|
|
|
|
|
scrollbar_option_menu = gtk_option_menu_new();
|
|
|
|
|
gtk_option_menu_set_menu( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
scrollbar_menu );
|
|
|
|
|
gtk_option_menu_set_history( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
temp_gui_scrollbar_on_right);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), scrollbar_option_menu,
|
|
|
|
|
1, 2, 0, 1 );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
/* Packet list selection browseable */
|
|
|
|
|
label = gtk_label_new("Packet-list selection bar movement:");
|
|
|
|
|
gtk_misc_set_alignment( GTK_MISC(label), 1.0, 0.5 );
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), label, 0, 1, 1, 2 );
|
|
|
|
|
|
|
|
|
|
/* Create a simple menu containing the LEFT/RIGHT choices */
|
|
|
|
|
scrollbar_menu = gtk_menu_new();
|
1999-12-30 23:02:56 +00:00
|
|
|
menu_item_false = gtk_menu_item_new_with_label("Selects");
|
|
|
|
|
menu_item_true = gtk_menu_item_new_with_label("Browses");
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_false );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_true );
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_false), "activate",
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
plist_sel_browse_cb, GINT_TO_POINTER(FALSE) );
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_true), "activate",
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
plist_sel_browse_cb, GINT_TO_POINTER(TRUE) );
|
|
|
|
|
|
|
|
|
|
/* Create the option menu from the option */
|
|
|
|
|
scrollbar_option_menu = gtk_option_menu_new();
|
|
|
|
|
gtk_option_menu_set_menu( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
scrollbar_menu );
|
|
|
|
|
gtk_option_menu_set_history( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
temp_gui_plist_sel_browse);
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), scrollbar_option_menu,
|
|
|
|
|
1, 2, 1, 2 );
|
|
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
/* Proto tree selection browseable */
|
|
|
|
|
label = gtk_label_new("Protocol-tree selection bar movement:");
|
|
|
|
|
gtk_misc_set_alignment( GTK_MISC(label), 1.0, 0.5 );
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), label, 0, 1, 2, 3 );
|
|
|
|
|
|
|
|
|
|
/* Create a simple menu containing the LEFT/RIGHT choices */
|
|
|
|
|
scrollbar_menu = gtk_menu_new();
|
1999-12-30 23:02:56 +00:00
|
|
|
menu_item_false = gtk_menu_item_new_with_label("Selects");
|
|
|
|
|
menu_item_true = gtk_menu_item_new_with_label("Browses");
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_false );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_true );
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_false), "activate",
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
ptree_sel_browse_cb, GINT_TO_POINTER(FALSE) );
|
1999-12-30 23:02:56 +00:00
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_true), "activate",
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
ptree_sel_browse_cb, GINT_TO_POINTER(TRUE) );
|
|
|
|
|
|
|
|
|
|
/* Create the option menu from the option */
|
|
|
|
|
scrollbar_option_menu = gtk_option_menu_new();
|
|
|
|
|
gtk_option_menu_set_menu( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
scrollbar_menu );
|
|
|
|
|
gtk_option_menu_set_history( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
temp_gui_ptree_sel_browse);
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), scrollbar_option_menu,
|
|
|
|
|
1, 2, 2, 3 );
|
1999-12-16 06:20:18 +00:00
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
|
|
|
|
|
/* Proto tree line style */
|
|
|
|
|
label = gtk_label_new("Protocol-tree line style:");
|
|
|
|
|
gtk_misc_set_alignment( GTK_MISC(label), 1.0, 0.5 );
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), label, 0, 1, 3, 4 );
|
|
|
|
|
|
|
|
|
|
/* Create a menu */
|
|
|
|
|
scrollbar_menu = gtk_menu_new();
|
|
|
|
|
menu_item_0 = gtk_menu_item_new_with_label("None");
|
|
|
|
|
menu_item_1 = gtk_menu_item_new_with_label("Solid");
|
|
|
|
|
menu_item_2 = gtk_menu_item_new_with_label("Dotted");
|
|
|
|
|
menu_item_3 = gtk_menu_item_new_with_label("Tabbed");
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_0 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_1 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_2 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_3 );
|
|
|
|
|
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_0), "activate",
|
|
|
|
|
ptree_line_style_cb, GINT_TO_POINTER(0) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_1), "activate",
|
|
|
|
|
ptree_line_style_cb, GINT_TO_POINTER(1) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_2), "activate",
|
|
|
|
|
ptree_line_style_cb, GINT_TO_POINTER(2) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_3), "activate",
|
|
|
|
|
ptree_line_style_cb, GINT_TO_POINTER(3) );
|
|
|
|
|
|
|
|
|
|
/* Create the option menu from the option */
|
|
|
|
|
scrollbar_option_menu = gtk_option_menu_new();
|
|
|
|
|
gtk_option_menu_set_menu( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
scrollbar_menu );
|
|
|
|
|
gtk_option_menu_set_history( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
temp_gui_ptree_line_style);
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), scrollbar_option_menu,
|
|
|
|
|
1, 2, 3, 4 );
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* Proto tree expander style */
|
|
|
|
|
label = gtk_label_new("Protocol-tree expander style:");
|
|
|
|
|
gtk_misc_set_alignment( GTK_MISC(label), 1.0, 0.5 );
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), label, 0, 1, 4, 5 );
|
|
|
|
|
|
|
|
|
|
/* Create a menu */
|
|
|
|
|
scrollbar_menu = gtk_menu_new();
|
|
|
|
|
menu_item_0 = gtk_menu_item_new_with_label("None");
|
|
|
|
|
menu_item_1 = gtk_menu_item_new_with_label("Square");
|
|
|
|
|
menu_item_2 = gtk_menu_item_new_with_label("Triangle");
|
|
|
|
|
menu_item_3 = gtk_menu_item_new_with_label("Circular");
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_0 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_1 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_2 );
|
|
|
|
|
gtk_menu_append( GTK_MENU(scrollbar_menu), menu_item_3 );
|
|
|
|
|
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_0), "activate",
|
|
|
|
|
ptree_expander_style_cb, GINT_TO_POINTER(0) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_1), "activate",
|
|
|
|
|
ptree_expander_style_cb, GINT_TO_POINTER(1) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_2), "activate",
|
|
|
|
|
ptree_expander_style_cb, GINT_TO_POINTER(2) );
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(menu_item_3), "activate",
|
|
|
|
|
ptree_expander_style_cb, GINT_TO_POINTER(3) );
|
|
|
|
|
|
|
|
|
|
/* Create the option menu from the option */
|
|
|
|
|
scrollbar_option_menu = gtk_option_menu_new();
|
|
|
|
|
gtk_option_menu_set_menu( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
scrollbar_menu );
|
|
|
|
|
gtk_option_menu_set_history( GTK_OPTION_MENU(scrollbar_option_menu),
|
|
|
|
|
temp_gui_ptree_expander_style);
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), scrollbar_option_menu,
|
|
|
|
|
1, 2, 4, 5 );
|
|
|
|
|
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
/* "Font..." button - click to open a font selection dialog box. */
|
|
|
|
|
font_bt = gtk_button_new_with_label("Font...");
|
|
|
|
|
gtk_signal_connect(GTK_OBJECT(font_bt), "clicked",
|
|
|
|
|
GTK_SIGNAL_FUNC(font_browse_cb), NULL);
|
|
|
|
|
gtk_table_attach_defaults( GTK_TABLE(main_tb), font_bt, 1, 2, 5, 6 );
|
|
|
|
|
|
1999-12-16 06:20:18 +00:00
|
|
|
/* Show 'em what we got */
|
|
|
|
|
gtk_widget_show_all(main_vb);
|
|
|
|
|
|
|
|
|
|
return(main_vb);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
scrollbar_menu_item_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
gboolean value = GPOINTER_TO_INT(data);
|
|
|
|
|
|
|
|
|
|
temp_gui_scrollbar_on_right = value;
|
2000-02-29 06:24:41 +00:00
|
|
|
set_scrollbar_placement_all(value);
|
1999-12-16 06:20:18 +00:00
|
|
|
}
|
|
|
|
|
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
static void
|
|
|
|
|
plist_sel_browse_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
gboolean value = GPOINTER_TO_INT(data);
|
|
|
|
|
|
|
|
|
|
temp_gui_plist_sel_browse = value;
|
|
|
|
|
set_plist_sel_browse(value);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
ptree_sel_browse_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
gboolean value = GPOINTER_TO_INT(data);
|
|
|
|
|
|
|
|
|
|
temp_gui_ptree_sel_browse = value;
|
2000-02-29 06:24:41 +00:00
|
|
|
set_ptree_sel_browse_all(value);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
}
|
|
|
|
|
|
1999-12-30 23:02:56 +00:00
|
|
|
static void
|
|
|
|
|
ptree_line_style_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
gint value = GPOINTER_TO_INT(data);
|
|
|
|
|
|
|
|
|
|
temp_gui_ptree_line_style = value;
|
2000-02-29 06:24:41 +00:00
|
|
|
set_ptree_line_style_all(value);
|
1999-12-30 23:02:56 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
ptree_expander_style_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
gint value = GPOINTER_TO_INT(data);
|
|
|
|
|
|
|
|
|
|
temp_gui_ptree_expander_style = value;
|
2000-02-29 06:24:41 +00:00
|
|
|
set_ptree_expander_style_all(value);
|
1999-12-30 23:02:56 +00:00
|
|
|
}
|
|
|
|
|
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
/* XXX - need a way to set this on the fly, so that a font change takes
|
|
|
|
|
effect immediately, rather than requiring the user to exit and restart
|
|
|
|
|
Ethereal. */
|
|
|
|
|
|
|
|
|
|
/* Create a font dialog for browsing. */
|
|
|
|
|
static void
|
|
|
|
|
font_browse_cb(GtkWidget *w, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
GtkWidget *caller = gtk_widget_get_toplevel(w);
|
|
|
|
|
GtkWidget *font_browse_w;
|
|
|
|
|
static gchar *fixedwidths[] = { "c", "m", NULL };
|
|
|
|
|
|
|
|
|
|
/* Has a font dialog box already been opened for that top-level
|
|
|
|
|
widget? */
|
|
|
|
|
font_browse_w = gtk_object_get_data(GTK_OBJECT(caller),
|
|
|
|
|
E_FONT_DIALOG_PTR_KEY);
|
|
|
|
|
|
|
|
|
|
if (font_browse_w != NULL) {
|
|
|
|
|
/* Yes. Just re-activate that dialog box. */
|
|
|
|
|
reactivate_window(font_browse_w);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Now create a new dialog. */
|
|
|
|
|
font_browse_w = gtk_font_selection_dialog_new("Ethereal: Select Font");
|
|
|
|
|
gtk_window_set_transient_for(GTK_WINDOW(font_browse_w),
|
|
|
|
|
GTK_WINDOW(top_level));
|
|
|
|
|
|
|
|
|
|
/* Call a handler when we're destroyed, so we can inform
|
|
|
|
|
our caller, if any, that we've been destroyed. */
|
|
|
|
|
gtk_signal_connect(GTK_OBJECT(font_browse_w), "destroy",
|
|
|
|
|
GTK_SIGNAL_FUNC(font_browse_destroy), NULL);
|
|
|
|
|
|
|
|
|
|
/* Set its filter to show only fixed_width fonts. */
|
|
|
|
|
gtk_font_selection_dialog_set_filter(
|
|
|
|
|
GTK_FONT_SELECTION_DIALOG(font_browse_w),
|
|
|
|
|
GTK_FONT_FILTER_BASE, /* user can't change the filter */
|
|
|
|
|
GTK_FONT_ALL, /* bitmap or scalable are fine */
|
|
|
|
|
NULL, /* all foundries are OK */
|
|
|
|
|
NULL, /* all weights are OK (XXX - normal only?) */
|
|
|
|
|
NULL, /* all slants are OK (XXX - Roman only?) */
|
|
|
|
|
NULL, /* all setwidths are OK */
|
|
|
|
|
fixedwidths, /* ONLY fixed-width fonts */
|
|
|
|
|
NULL); /* all charsets are OK (XXX - ISO 8859/1 only?) */
|
|
|
|
|
|
|
|
|
|
/* Set the font to the current font.
|
|
|
|
|
XXX - this doesn't seem to work right. */
|
|
|
|
|
gtk_font_selection_dialog_set_font_name(
|
|
|
|
|
GTK_FONT_SELECTION_DIALOG(font_browse_w), prefs.gui_font_name);
|
|
|
|
|
|
|
|
|
|
/* Set the E_FONT_CALLER_PTR_KEY for the new dialog to point to
|
|
|
|
|
our caller. */
|
|
|
|
|
gtk_object_set_data(GTK_OBJECT(font_browse_w), E_FONT_CALLER_PTR_KEY,
|
|
|
|
|
caller);
|
|
|
|
|
|
|
|
|
|
/* Set the E_FONT_DIALOG_PTR_KEY for the caller to point to us */
|
|
|
|
|
gtk_object_set_data(GTK_OBJECT(caller), E_FONT_DIALOG_PTR_KEY,
|
|
|
|
|
font_browse_w);
|
|
|
|
|
|
|
|
|
|
/* Connect the ok_button to font_browse_ok_cb function and pass along a
|
|
|
|
|
pointer to the font selection box widget */
|
|
|
|
|
gtk_signal_connect(
|
|
|
|
|
GTK_OBJECT(GTK_FONT_SELECTION_DIALOG(font_browse_w)->ok_button),
|
|
|
|
|
"clicked", (GtkSignalFunc)font_browse_ok_cb, font_browse_w);
|
|
|
|
|
|
|
|
|
|
/* Connect the cancel_button to destroy the widget */
|
|
|
|
|
gtk_signal_connect_object(
|
|
|
|
|
GTK_OBJECT(GTK_FONT_SELECTION_DIALOG(font_browse_w)->cancel_button),
|
|
|
|
|
"clicked", (GtkSignalFunc)gtk_widget_destroy,
|
|
|
|
|
GTK_OBJECT(font_browse_w));
|
|
|
|
|
|
|
|
|
|
/* Catch the "key_press_event" signal in the window, so that we can
|
|
|
|
|
catch the ESC key being pressed and act as if the "Cancel" button
|
|
|
|
|
had been selected. */
|
|
|
|
|
dlg_set_cancel(font_browse_w,
|
|
|
|
|
GTK_FONT_SELECTION_DIALOG(font_browse_w)->cancel_button);
|
|
|
|
|
|
|
|
|
|
gtk_widget_show(font_browse_w);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
font_browse_ok_cb(GtkWidget *w, GtkFontSelectionDialog *fs)
|
|
|
|
|
{
|
|
|
|
|
if (temp_gui_font_name != NULL)
|
|
|
|
|
g_free(temp_gui_font_name);
|
|
|
|
|
temp_gui_font_name =
|
|
|
|
|
g_strdup(gtk_font_selection_dialog_get_font_name(
|
|
|
|
|
GTK_FONT_SELECTION_DIALOG(fs)));
|
|
|
|
|
|
|
|
|
|
gtk_widget_hide(GTK_WIDGET(fs));
|
|
|
|
|
gtk_widget_destroy(GTK_WIDGET(fs));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
font_browse_destroy(GtkWidget *win, gpointer data)
|
|
|
|
|
{
|
|
|
|
|
GtkWidget *caller;
|
|
|
|
|
|
|
|
|
|
/* Get the widget that requested that we be popped up, if any.
|
|
|
|
|
(It should arrange to destroy us if it's destroyed, so
|
|
|
|
|
that we don't get a pointer to a non-existent window here.) */
|
|
|
|
|
caller = gtk_object_get_data(GTK_OBJECT(win), E_FONT_CALLER_PTR_KEY);
|
|
|
|
|
|
|
|
|
|
if (caller != NULL) {
|
|
|
|
|
/* Tell it we no longer exist. */
|
|
|
|
|
gtk_object_set_data(GTK_OBJECT(caller), E_FONT_DIALOG_PTR_KEY,
|
|
|
|
|
NULL);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Now nuke this window. */
|
|
|
|
|
gtk_grab_remove(GTK_WIDGET(win));
|
|
|
|
|
gtk_widget_destroy(GTK_WIDGET(win));
|
|
|
|
|
}
|
1999-12-30 23:02:56 +00:00
|
|
|
|
1999-12-16 06:20:18 +00:00
|
|
|
void
|
|
|
|
|
gui_prefs_ok(GtkWidget *w)
|
|
|
|
|
{
|
|
|
|
|
prefs.gui_scrollbar_on_right = temp_gui_scrollbar_on_right;
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
prefs.gui_plist_sel_browse = temp_gui_plist_sel_browse;
|
|
|
|
|
prefs.gui_ptree_sel_browse = temp_gui_ptree_sel_browse;
|
1999-12-30 23:02:56 +00:00
|
|
|
prefs.gui_ptree_line_style = temp_gui_ptree_line_style;
|
|
|
|
|
prefs.gui_ptree_expander_style = temp_gui_ptree_expander_style;
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
if (prefs.gui_font_name != NULL)
|
|
|
|
|
g_free(prefs.gui_font_name);
|
|
|
|
|
prefs.gui_font_name = g_strdup(temp_gui_font_name);
|
1999-12-30 23:02:56 +00:00
|
|
|
|
1999-12-16 06:20:18 +00:00
|
|
|
gui_prefs_delete(w);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
gui_prefs_save(GtkWidget *w)
|
|
|
|
|
{
|
|
|
|
|
gui_prefs_ok(w);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
gui_prefs_cancel(GtkWidget *w)
|
|
|
|
|
{
|
2000-02-29 06:24:41 +00:00
|
|
|
/* Reset GUI preference values back to what the
|
|
|
|
|
* current preferences says they should be */
|
1999-12-16 06:20:18 +00:00
|
|
|
temp_gui_scrollbar_on_right = prefs.gui_scrollbar_on_right;
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
temp_gui_plist_sel_browse = prefs.gui_plist_sel_browse;
|
|
|
|
|
temp_gui_ptree_sel_browse = prefs.gui_ptree_sel_browse;
|
1999-12-30 23:02:56 +00:00
|
|
|
temp_gui_ptree_line_style = prefs.gui_ptree_line_style;
|
|
|
|
|
temp_gui_ptree_expander_style = prefs.gui_ptree_expander_style;
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
if (temp_gui_font_name != NULL)
|
|
|
|
|
g_free(temp_gui_font_name);
|
|
|
|
|
temp_gui_font_name = g_strdup(prefs.gui_font_name);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
|
2000-02-29 06:24:41 +00:00
|
|
|
set_scrollbar_placement_all(prefs.gui_scrollbar_on_right);
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
set_plist_sel_browse(prefs.gui_plist_sel_browse);
|
2000-02-29 06:24:41 +00:00
|
|
|
set_ptree_sel_browse_all(prefs.gui_ptree_sel_browse);
|
|
|
|
|
set_ptree_line_style_all(prefs.gui_ptree_line_style);
|
|
|
|
|
set_ptree_expander_style_all(prefs.gui_ptree_expander_style);
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
|
|
|
gui_prefs_delete(w);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
gui_prefs_delete(GtkWidget *w)
|
|
|
|
|
{
|
Instead of having the normal-weight and bold fonts set separately,
generate the name of the boldface font from the Roman font; if the two
fonts don't have the same widths, the display will look weird when a
field is selected, and it's a bit of a pain for the user to have to
select *two* fonts.
On UNIX/X, default to
"-*-fixed-medium-r-semicondensed-*-*-120-*-*-*-*-*-" rather than to
"-*-lucidatypewriter-medium-r-normal-*-*-120-*-*-*-*-iso8859-1" - some
Linux distributions appear to lack the Lucida typewriter font.
Add a "gui.font_name" preference to the preferences file, specifying the
normal-weight font to use. Have it settable from the "GUI" tab in the
Preferences dialog box - the "Font..." button, when clicked, pops up a
font selection dialog box.
If we either can't open the selected font or the boldfaced version of
the font, default to "6x13" and "6x13bold" as fallbacks - the former
will probably be "fixed", and the latter would be "fixedbold" if X
actually created such an alias, but it doesn't so we use "6x13bold"
instead.
svn path=/trunk/; revision=2304
2000-08-20 07:53:45 +00:00
|
|
|
GtkWidget *caller = gtk_widget_get_toplevel(w);
|
|
|
|
|
GtkWidget *fs;
|
|
|
|
|
|
|
|
|
|
/* Is there a font selection dialog associated with this
|
|
|
|
|
Preferences dialog? */
|
|
|
|
|
fs = gtk_object_get_data(GTK_OBJECT(caller), E_FONT_DIALOG_PTR_KEY);
|
|
|
|
|
|
|
|
|
|
if (fs != NULL) {
|
|
|
|
|
/* Yes. Destroy it. */
|
|
|
|
|
gtk_widget_destroy(fs);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (temp_gui_font_name != NULL) {
|
|
|
|
|
g_free(temp_gui_font_name);
|
|
|
|
|
temp_gui_font_name = NULL;
|
|
|
|
|
}
|
1999-12-16 06:20:18 +00:00
|
|
|
}
|