2000-09-08 09:50:08 +00:00
|
|
|
/* proto_draw.c
|
1999-03-23 03:14:46 +00:00
|
|
|
* Routines for GTK+ packet display
|
|
|
|
*
|
2000-09-08 10:59:21 +00:00
|
|
|
* $Id: proto_draw.c,v 1.20 2000/09/08 10:59:19 guy Exp $
|
1999-03-23 03:14:46 +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
|
|
|
|
|
|
|
|
#ifdef HAVE_SYS_TYPES_H
|
|
|
|
# include <sys/types.h>
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include <ctype.h>
|
|
|
|
#include <stdarg.h>
|
|
|
|
|
|
|
|
#include <gtk/gtk.h>
|
|
|
|
|
1999-03-23 03:54:46 +00:00
|
|
|
#ifdef NEED_SNPRINTF_H
|
|
|
|
# include "snprintf.h"
|
|
|
|
#endif
|
|
|
|
|
1999-03-23 19:41:51 +00:00
|
|
|
#include <stdio.h>
|
1999-09-09 02:42:40 +00:00
|
|
|
#include "main.h"
|
1999-03-23 03:14:46 +00:00
|
|
|
#include "packet.h"
|
1999-11-22 06:24:56 +00:00
|
|
|
#include "util.h"
|
1999-03-23 03:14:46 +00:00
|
|
|
|
2000-02-29 06:24:41 +00:00
|
|
|
#include "prefs.h"
|
1999-09-09 02:42:40 +00:00
|
|
|
#include "proto_draw.h"
|
2000-09-08 09:50:08 +00:00
|
|
|
#include "packet_win.h"
|
2000-02-29 06:24:41 +00:00
|
|
|
#include "gtkglobals.h"
|
1999-03-23 03:14:46 +00:00
|
|
|
|
|
|
|
#define BYTE_VIEW_WIDTH 16
|
1999-04-16 18:39:07 +00:00
|
|
|
#define BYTE_VIEW_SEP 8
|
1999-03-23 03:14:46 +00:00
|
|
|
|
|
|
|
extern GdkFont *m_r_font, *m_b_font;
|
|
|
|
|
1999-07-07 22:52:57 +00:00
|
|
|
static void
|
|
|
|
proto_tree_draw_node(GNode *node, gpointer data);
|
|
|
|
|
2000-09-08 10:59:21 +00:00
|
|
|
/* Redraw a given byte view window. */
|
2000-09-08 09:50:08 +00:00
|
|
|
void
|
2000-09-08 10:59:21 +00:00
|
|
|
redraw_hex_dump(GtkWidget *bv, field_info *finfo)
|
2000-09-08 09:50:08 +00:00
|
|
|
{
|
|
|
|
if (finfo != NULL) {
|
|
|
|
packet_hex_print(GTK_TEXT(bv), cfile.pd, cfile.current_frame->cap_len,
|
|
|
|
finfo->start, finfo->length,
|
2000-09-08 10:59:21 +00:00
|
|
|
cfile.current_frame->flags.encoding);
|
2000-09-08 09:50:08 +00:00
|
|
|
} else {
|
|
|
|
packet_hex_print(GTK_TEXT(bv), cfile.pd, cfile.current_frame->cap_len,
|
2000-09-08 10:59:21 +00:00
|
|
|
-1, -1, cfile.current_frame->flags.encoding);
|
2000-09-08 09:50:08 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2000-09-08 10:59:21 +00:00
|
|
|
redraw_hex_dump_all(void)
|
2000-09-08 09:50:08 +00:00
|
|
|
{
|
2000-09-08 10:59:21 +00:00
|
|
|
redraw_hex_dump(byte_view, finfo_selected);
|
|
|
|
redraw_hex_dump_packet_wins();
|
2000-09-08 09:50:08 +00:00
|
|
|
}
|
|
|
|
|
2000-02-29 06:24:41 +00:00
|
|
|
void
|
|
|
|
create_byte_view(gint bv_size, GtkWidget *pane, GtkWidget **byte_view_p,
|
2000-03-02 07:05:57 +00:00
|
|
|
GtkWidget **bv_scrollw_p, int pos)
|
2000-02-29 06:24:41 +00:00
|
|
|
{
|
2000-03-02 07:05:57 +00:00
|
|
|
GtkWidget *byte_view, *byte_scrollw;
|
|
|
|
|
|
|
|
/* Byte view. Create a scrolled window for the text. */
|
|
|
|
byte_scrollw = gtk_scrolled_window_new(NULL, NULL);
|
|
|
|
gtk_paned_pack2(GTK_PANED(pane), byte_scrollw, FALSE, FALSE);
|
|
|
|
gtk_widget_set_usize(byte_scrollw, -1, bv_size);
|
|
|
|
gtk_scrolled_window_set_policy(GTK_SCROLLED_WINDOW(byte_scrollw),
|
|
|
|
GTK_POLICY_NEVER,
|
|
|
|
GTK_POLICY_ALWAYS);
|
|
|
|
set_scrollbar_placement_scrollw(byte_scrollw, pos);
|
|
|
|
remember_scrolled_window(byte_scrollw);
|
|
|
|
gtk_widget_show(byte_scrollw);
|
2000-02-29 06:24:41 +00:00
|
|
|
|
|
|
|
byte_view = gtk_text_new(NULL, NULL);
|
|
|
|
gtk_text_set_editable(GTK_TEXT(byte_view), FALSE);
|
|
|
|
gtk_text_set_word_wrap(GTK_TEXT(byte_view), FALSE);
|
2000-03-02 07:05:57 +00:00
|
|
|
gtk_container_add(GTK_CONTAINER(byte_scrollw), byte_view);
|
2000-02-29 06:24:41 +00:00
|
|
|
gtk_widget_show(byte_view);
|
|
|
|
|
|
|
|
*byte_view_p = byte_view;
|
2000-03-02 07:05:57 +00:00
|
|
|
*bv_scrollw_p = byte_scrollw;
|
2000-02-29 06:24:41 +00:00
|
|
|
}
|
|
|
|
|
1999-03-23 03:14:46 +00:00
|
|
|
void
|
1999-11-22 06:24:56 +00:00
|
|
|
packet_hex_print(GtkText *bv, guint8 *pd, gint len, gint bstart, gint blen,
|
2000-09-08 10:59:21 +00:00
|
|
|
char_enc encoding) {
|
1999-03-23 03:14:46 +00:00
|
|
|
gint i = 0, j, k, cur;
|
2000-04-27 20:39:21 +00:00
|
|
|
guchar line[128], hexchars[] = "0123456789abcdef", c = '\0';
|
1999-03-23 03:14:46 +00:00
|
|
|
GdkFont *cur_font, *new_font;
|
1999-12-14 06:52:09 +00:00
|
|
|
gint bend = -1;
|
1999-11-22 06:24:56 +00:00
|
|
|
|
2000-09-08 09:50:08 +00:00
|
|
|
GdkColor *fg, *bg;
|
|
|
|
gboolean reverse, newreverse;
|
|
|
|
|
1999-12-03 21:28:58 +00:00
|
|
|
/* Freeze the text for faster display */
|
|
|
|
gtk_text_freeze(bv);
|
|
|
|
|
|
|
|
/* Clear out the text */
|
|
|
|
gtk_text_set_point(bv, 0);
|
2000-01-25 03:45:45 +00:00
|
|
|
/* Keep GTK+ 1.2.3 through 1.2.6 from dumping core - see
|
|
|
|
http://ethereal.zing.org/lists/ethereal-dev/199912/msg00312.html and
|
|
|
|
http://www.gnome.org/mailing-lists/archives/gtk-devel-list/1999-October/0051.shtml
|
|
|
|
for more information */
|
|
|
|
gtk_adjustment_set_value(bv->vadj, 0.0);
|
1999-12-03 21:28:58 +00:00
|
|
|
gtk_text_forward_delete(bv, gtk_text_get_length(bv));
|
|
|
|
|
1999-12-14 06:52:09 +00:00
|
|
|
if (bstart >= 0 && blen >= 0) {
|
|
|
|
bend = bstart + blen;
|
|
|
|
}
|
|
|
|
|
1999-03-23 03:14:46 +00:00
|
|
|
while (i < len) {
|
|
|
|
/* Print the line number */
|
|
|
|
sprintf(line, "%04x ", i);
|
2000-09-08 09:50:08 +00:00
|
|
|
|
|
|
|
/* Display with inverse video ? */
|
2000-09-08 10:59:21 +00:00
|
|
|
if (prefs.gui_hex_dump_highlight_style) {
|
2000-09-08 09:50:08 +00:00
|
|
|
gtk_text_insert(bv, m_r_font, &BLACK, &WHITE, line, -1);
|
|
|
|
/* Do we start in reverse? */
|
|
|
|
reverse = i >= bstart && i < bend;
|
|
|
|
fg = reverse ? &WHITE : &BLACK;
|
|
|
|
bg = reverse ? &BLACK : &WHITE;
|
|
|
|
j = i;
|
|
|
|
k = i + BYTE_VIEW_WIDTH;
|
|
|
|
cur = 0;
|
|
|
|
/* Print the hex bit */
|
|
|
|
while (i < k) {
|
|
|
|
if (i < len) {
|
|
|
|
line[cur++] = hexchars[(pd[i] & 0xf0) >> 4];
|
|
|
|
line[cur++] = hexchars[pd[i] & 0x0f];
|
|
|
|
} else {
|
|
|
|
line[cur++] = ' '; line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
newreverse = i >= bstart && i < bend;
|
|
|
|
/* Have we gone from reverse to plain? */
|
|
|
|
if (reverse && (reverse != newreverse)) {
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
fg = &BLACK;
|
|
|
|
bg = &WHITE;
|
|
|
|
cur = 0;
|
|
|
|
}
|
|
|
|
/* Inter byte space if not at end of line */
|
|
|
|
if (i < k) {
|
|
|
|
line[cur++] = ' ';
|
|
|
|
/* insert a space every BYTE_VIEW_SEP bytes */
|
|
|
|
if( ( i % BYTE_VIEW_SEP ) == 0 ) {
|
|
|
|
line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* Have we gone from plain to reversed? */
|
|
|
|
if (!reverse && (reverse != newreverse)) {
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
fg = &WHITE;
|
|
|
|
bg = &BLACK;
|
|
|
|
cur = 0;
|
|
|
|
}
|
|
|
|
reverse = newreverse;
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
2000-09-08 09:50:08 +00:00
|
|
|
/* Print remaining part of line */
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
cur = 0;
|
|
|
|
/* Print some space at the end of the line */
|
|
|
|
line[cur++] = ' '; line[cur++] = ' '; line[cur++] = ' ';
|
|
|
|
gtk_text_insert(bv, m_r_font, &BLACK, &WHITE, line, cur);
|
|
|
|
cur = 0;
|
|
|
|
|
|
|
|
/* Print the ASCII bit */
|
|
|
|
i = j;
|
|
|
|
/* Do we start in reverse? */
|
|
|
|
reverse = i >= bstart && i < bend;
|
|
|
|
fg = reverse ? &WHITE : &BLACK;
|
|
|
|
bg = reverse ? &BLACK : &WHITE;
|
|
|
|
while (i < k) {
|
|
|
|
if (i < len) {
|
|
|
|
if (encoding == CHAR_ASCII) {
|
|
|
|
c = pd[i];
|
|
|
|
}
|
|
|
|
else if (encoding == CHAR_EBCDIC) {
|
|
|
|
c = EBCDIC_to_ASCII1(pd[i]);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
g_assert_not_reached();
|
|
|
|
}
|
|
|
|
line[cur++] = (isprint(c)) ? c : '.';
|
|
|
|
} else {
|
|
|
|
line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
newreverse = i >= bstart && i < bend;
|
|
|
|
/* Have we gone from reverse to plain? */
|
|
|
|
if (reverse && (reverse != newreverse)) {
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
fg = &BLACK;
|
|
|
|
bg = &WHITE;
|
|
|
|
cur = 0;
|
|
|
|
}
|
|
|
|
if (i < k) {
|
|
|
|
/* insert a space every BYTE_VIEW_SEP bytes */
|
|
|
|
if( ( i % BYTE_VIEW_SEP ) == 0 ) {
|
|
|
|
line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* Have we gone from plain to reversed? */
|
|
|
|
if (!reverse && (reverse != newreverse)) {
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
fg = &WHITE;
|
|
|
|
bg = &BLACK;
|
|
|
|
cur = 0;
|
|
|
|
}
|
|
|
|
reverse = newreverse;
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
2000-09-08 09:50:08 +00:00
|
|
|
/* Print remaining part of line */
|
|
|
|
gtk_text_insert(bv, m_r_font, fg, bg, line, cur);
|
|
|
|
cur = 0;
|
|
|
|
line[cur++] = '\n';
|
|
|
|
line[cur] = '\0';
|
|
|
|
gtk_text_insert(bv, m_r_font, &BLACK, &WHITE, line, -1);
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
2000-09-08 09:50:08 +00:00
|
|
|
else {
|
|
|
|
gtk_text_insert(bv, m_r_font, NULL, NULL, line, -1);
|
|
|
|
/* Do we start in bold? */
|
|
|
|
cur_font = (i >= bstart && i < bend) ? m_b_font : m_r_font;
|
|
|
|
j = i;
|
|
|
|
k = i + BYTE_VIEW_WIDTH;
|
|
|
|
cur = 0;
|
|
|
|
/* Print the hex bit */
|
|
|
|
while (i < k) {
|
|
|
|
if (i < len) {
|
|
|
|
line[cur++] = hexchars[(pd[i] & 0xf0) >> 4];
|
|
|
|
line[cur++] = hexchars[pd[i] & 0x0f];
|
|
|
|
} else {
|
|
|
|
line[cur++] = ' '; line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
line[cur++] = ' ';
|
|
|
|
i++;
|
|
|
|
/* insert a space every BYTE_VIEW_SEP bytes */
|
|
|
|
if( ( i % BYTE_VIEW_SEP ) == 0 ) line[cur++] = ' ';
|
|
|
|
/* Did we cross a bold/plain boundary? */
|
|
|
|
new_font = (i >= bstart && i < bend) ? m_b_font : m_r_font;
|
|
|
|
if (cur_font != new_font) {
|
|
|
|
gtk_text_insert(bv, cur_font, NULL, NULL, line, cur);
|
|
|
|
cur_font = new_font;
|
|
|
|
cur = 0;
|
|
|
|
}
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
2000-09-08 09:50:08 +00:00
|
|
|
line[cur++] = ' ';
|
|
|
|
gtk_text_insert(bv, cur_font, NULL, NULL, line, cur);
|
|
|
|
|
|
|
|
cur = 0;
|
|
|
|
i = j;
|
|
|
|
/* Print the ASCII bit */
|
|
|
|
cur_font = (i >= bstart && i < bend) ? m_b_font : m_r_font;
|
|
|
|
while (i < k) {
|
|
|
|
if (i < len) {
|
|
|
|
if (encoding == CHAR_ASCII) {
|
|
|
|
c = pd[i];
|
|
|
|
}
|
|
|
|
else if (encoding == CHAR_EBCDIC) {
|
|
|
|
c = EBCDIC_to_ASCII1(pd[i]);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
g_assert_not_reached();
|
|
|
|
}
|
|
|
|
line[cur++] = (isprint(c)) ? c : '.';
|
|
|
|
} else {
|
|
|
|
line[cur++] = ' ';
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
/* insert a space every BYTE_VIEW_SEP bytes */
|
|
|
|
if( ( i % BYTE_VIEW_SEP ) == 0 ) line[cur++] = ' ';
|
|
|
|
/* Did we cross a bold/plain boundary? */
|
|
|
|
new_font = (i >= bstart && i < bend) ? m_b_font : m_r_font;
|
|
|
|
if (cur_font != new_font) {
|
|
|
|
gtk_text_insert(bv, cur_font, NULL, NULL, line, cur);
|
|
|
|
cur_font = new_font;
|
|
|
|
cur = 0;
|
|
|
|
}
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
2000-09-08 09:50:08 +00:00
|
|
|
line[cur++] = '\n';
|
|
|
|
line[cur] = '\0';
|
|
|
|
gtk_text_insert(bv, cur_font, NULL, NULL, line, -1);
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
|
|
|
}
|
1999-12-03 21:28:58 +00:00
|
|
|
|
|
|
|
/* scroll text into position */
|
|
|
|
gtk_text_thaw(bv); /* must thaw before adjusting scroll bars */
|
|
|
|
if ( bstart > 0 ) {
|
1999-12-14 06:52:09 +00:00
|
|
|
int lineheight, linenum;
|
|
|
|
float scrollval;
|
1999-12-03 21:28:58 +00:00
|
|
|
linenum = bstart / BYTE_VIEW_WIDTH;
|
|
|
|
|
|
|
|
/* need to change to some way of getting that offset instead of +4 */
|
|
|
|
lineheight = gdk_string_height(m_b_font, "0") + 4;
|
|
|
|
scrollval = MIN(linenum * lineheight,bv->vadj->upper - bv->vadj->page_size);
|
|
|
|
|
|
|
|
gtk_adjustment_set_value(bv->vadj, scrollval);
|
|
|
|
}
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
|
|
|
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2316
2000-08-21 08:09:17 +00:00
|
|
|
/* List of all protocol tree widgets, so we can globally set the selection
|
|
|
|
mode, line style, expander style, and font of all of them. */
|
|
|
|
static GList *ptree_widgets;
|
|
|
|
|
|
|
|
/* Add a protocol tree widget to the list of protocol tree widgets. */
|
|
|
|
static void forget_ptree_widget(GtkWidget *ptreew, gpointer data);
|
|
|
|
|
2000-09-08 09:50:08 +00:00
|
|
|
static void
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2316
2000-08-21 08:09:17 +00:00
|
|
|
remember_ptree_widget(GtkWidget *ptreew)
|
|
|
|
{
|
|
|
|
ptree_widgets = g_list_append(ptree_widgets, ptreew);
|
|
|
|
|
|
|
|
/* Catch the "destroy" event on the widget, so that we remove it from
|
|
|
|
the list when it's destroyed. */
|
|
|
|
gtk_signal_connect(GTK_OBJECT(ptreew), "destroy",
|
|
|
|
GTK_SIGNAL_FUNC(forget_ptree_widget), NULL);
|
|
|
|
}
|
|
|
|
|
2000-09-08 09:50:08 +00:00
|
|
|
/* Remove a protocol tree widget from the list of protocol tree widgets. */
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2316
2000-08-21 08:09:17 +00:00
|
|
|
static void
|
|
|
|
forget_ptree_widget(GtkWidget *ptreew, gpointer data)
|
|
|
|
{
|
|
|
|
ptree_widgets = g_list_remove(ptree_widgets, ptreew);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set the selection mode of a given packet tree window. */
|
|
|
|
static void
|
|
|
|
set_ptree_sel_browse(GtkWidget *ptreew, gboolean val)
|
|
|
|
{
|
|
|
|
/* Yeah, GTK uses "browse" in the case where we do not, but oh well.
|
|
|
|
I think "browse" in Ethereal makes more sense than "SINGLE" in
|
|
|
|
GTK+ */
|
|
|
|
if (val) {
|
|
|
|
gtk_clist_set_selection_mode(GTK_CLIST(ptreew),
|
|
|
|
GTK_SELECTION_SINGLE);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
gtk_clist_set_selection_mode(GTK_CLIST(ptreew),
|
|
|
|
GTK_SELECTION_BROWSE);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_ptree_sel_browse_cb(gpointer data, gpointer user_data)
|
|
|
|
{
|
|
|
|
set_ptree_sel_browse((GtkWidget *)data, *(gboolean *)user_data);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set the selection mode of all packet tree windows. */
|
|
|
|
void
|
|
|
|
set_ptree_sel_browse_all(gboolean val)
|
|
|
|
{
|
|
|
|
g_list_foreach(ptree_widgets, set_ptree_sel_browse_cb, &val);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set the line style of a given packet tree window. */
|
|
|
|
static void
|
|
|
|
set_ptree_line_style(GtkWidget *ptreew, gint style)
|
|
|
|
{
|
|
|
|
/* I'm using an assert here since the preferences code limits
|
|
|
|
* the user input, both in the GUI and when reading the preferences file.
|
|
|
|
* If the value is incorrect, it's a program error, not a user-initiated error.
|
|
|
|
*/
|
|
|
|
g_assert(style >= GTK_CTREE_LINES_NONE && style <= GTK_CTREE_LINES_TABBED);
|
|
|
|
gtk_ctree_set_line_style(GTK_CTREE(ptreew), style);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_ptree_line_style_cb(gpointer data, gpointer user_data)
|
|
|
|
{
|
|
|
|
set_ptree_line_style((GtkWidget *)data, *(gint *)user_data);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set the line style of all packet tree window. */
|
|
|
|
void
|
|
|
|
set_ptree_line_style_all(gint style)
|
|
|
|
{
|
|
|
|
g_list_foreach(ptree_widgets, set_ptree_line_style_cb, &style);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set the expander style of a given packet tree window. */
|
|
|
|
static void
|
|
|
|
set_ptree_expander_style(GtkWidget *ptreew, gint style)
|
|
|
|
{
|
|
|
|
/* I'm using an assert here since the preferences code limits
|
|
|
|
* the user input, both in the GUI and when reading the preferences file.
|
|
|
|
* If the value is incorrect, it's a program error, not a user-initiated error.
|
|
|
|
*/
|
|
|
|
g_assert(style >= GTK_CTREE_EXPANDER_NONE && style <= GTK_CTREE_EXPANDER_CIRCULAR);
|
|
|
|
gtk_ctree_set_expander_style(GTK_CTREE(ptreew), style);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_ptree_expander_style_cb(gpointer data, gpointer user_data)
|
|
|
|
{
|
|
|
|
set_ptree_expander_style((GtkWidget *)data, *(gint *)user_data);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
set_ptree_expander_style_all(gint style)
|
|
|
|
{
|
|
|
|
g_list_foreach(ptree_widgets, set_ptree_expander_style_cb, &style);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_ptree_style_cb(gpointer data, gpointer user_data)
|
|
|
|
{
|
|
|
|
gtk_widget_set_style((GtkWidget *)data, (GtkStyle *)user_data);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
set_ptree_font_all(GdkFont *font)
|
|
|
|
{
|
|
|
|
GtkStyle *style;
|
|
|
|
|
|
|
|
style = gtk_style_new();
|
|
|
|
gdk_font_unref(style->font);
|
|
|
|
style->font = font;
|
|
|
|
gdk_font_ref(font);
|
|
|
|
|
|
|
|
g_list_foreach(ptree_widgets, set_ptree_style_cb, style);
|
|
|
|
|
|
|
|
/* Now nuke the old style and replace it with the new one. */
|
|
|
|
gtk_style_unref(item_style);
|
|
|
|
item_style = style;
|
|
|
|
}
|
|
|
|
|
2000-02-29 06:24:41 +00:00
|
|
|
void
|
|
|
|
create_tree_view(gint tv_size, e_prefs *prefs, GtkWidget *pane,
|
2000-03-02 07:05:57 +00:00
|
|
|
GtkWidget **tv_scrollw_p, GtkWidget **tree_view_p, int pos)
|
2000-02-29 06:24:41 +00:00
|
|
|
{
|
|
|
|
GtkWidget *tv_scrollw, *tree_view;
|
|
|
|
|
|
|
|
/* Tree view */
|
|
|
|
tv_scrollw = gtk_scrolled_window_new(NULL, NULL);
|
|
|
|
gtk_scrolled_window_set_policy (GTK_SCROLLED_WINDOW(tv_scrollw),
|
|
|
|
GTK_POLICY_AUTOMATIC, GTK_POLICY_AUTOMATIC);
|
2000-03-02 07:05:57 +00:00
|
|
|
set_scrollbar_placement_scrollw(tv_scrollw, pos);
|
|
|
|
remember_scrolled_window(tv_scrollw);
|
2000-02-29 06:24:41 +00:00
|
|
|
gtk_paned_pack1(GTK_PANED(pane), tv_scrollw, TRUE, TRUE);
|
|
|
|
gtk_widget_set_usize(tv_scrollw, -1, tv_size);
|
|
|
|
gtk_widget_show(tv_scrollw);
|
|
|
|
|
|
|
|
tree_view = gtk_ctree_new(1, 0);
|
|
|
|
/* I need this next line to make the widget work correctly with hidden
|
|
|
|
* column titles and GTK_SELECTION_BROWSE */
|
|
|
|
gtk_clist_set_column_auto_resize( GTK_CLIST(tree_view), 0, TRUE );
|
|
|
|
gtk_container_add( GTK_CONTAINER(tv_scrollw), tree_view );
|
|
|
|
set_ptree_sel_browse(tree_view, prefs->gui_ptree_sel_browse);
|
|
|
|
set_ptree_line_style(tree_view, prefs->gui_ptree_line_style);
|
|
|
|
set_ptree_expander_style(tree_view, prefs->gui_ptree_expander_style);
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2316
2000-08-21 08:09:17 +00:00
|
|
|
gtk_widget_set_style(tree_view, item_style);
|
|
|
|
remember_ptree_widget(tree_view);
|
2000-02-29 06:24:41 +00:00
|
|
|
|
|
|
|
*tree_view_p = tree_view;
|
|
|
|
*tv_scrollw_p = tv_scrollw;
|
|
|
|
}
|
|
|
|
|
1999-09-11 12:38:18 +00:00
|
|
|
void expand_all_tree(proto_tree *protocol_tree, GtkWidget *tree_view) {
|
|
|
|
int i;
|
1999-11-16 11:44:20 +00:00
|
|
|
for(i=0; i < num_tree_types; i++) {
|
1999-09-12 20:23:43 +00:00
|
|
|
tree_is_expanded[i] = TRUE;
|
1999-09-11 12:38: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
|
|
|
gtk_clist_clear ( GTK_CLIST(tree_view) );
|
1999-09-11 12:38:18 +00:00
|
|
|
proto_tree_draw(protocol_tree, tree_view);
|
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_ctree_expand_recursive(GTK_CTREE(tree_view), NULL);
|
1999-09-11 12:38:18 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void collapse_all_tree(proto_tree *protocol_tree, GtkWidget *tree_view) {
|
|
|
|
int i;
|
1999-11-16 11:44:20 +00:00
|
|
|
for(i=0; i < num_tree_types; i++) {
|
1999-09-12 20:23:43 +00:00
|
|
|
tree_is_expanded[i] = FALSE;
|
1999-09-11 12:38: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
|
|
|
gtk_clist_clear ( GTK_CLIST(tree_view) );
|
1999-12-15 07:03:11 +00:00
|
|
|
proto_tree_draw(protocol_tree, tree_view);
|
1999-09-11 12:38:18 +00:00
|
|
|
}
|
|
|
|
|
1999-03-23 03:14:46 +00:00
|
|
|
static 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
|
|
|
expand_tree(GtkCTree *ctree, GList *node, gpointer user_data)
|
|
|
|
{
|
|
|
|
field_info *finfo;
|
|
|
|
gboolean *val;
|
1999-03-23 03:14:46 +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
|
|
|
finfo = gtk_ctree_node_get_row_data( ctree, GTK_CTREE_NODE(node) );
|
|
|
|
g_assert(finfo);
|
|
|
|
|
|
|
|
val = &tree_is_expanded[finfo->tree_type];
|
|
|
|
*val = TRUE;
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
|
|
|
|
1999-12-15 07:03:11 +00:00
|
|
|
static 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
|
|
|
collapse_tree(GtkCTree *ctree, GList *node, gpointer user_data)
|
1999-03-23 03:14:46 +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
|
|
|
field_info *finfo;
|
|
|
|
gboolean *val;
|
|
|
|
|
|
|
|
finfo = gtk_ctree_node_get_row_data( ctree, GTK_CTREE_NODE(node) );
|
|
|
|
g_assert(finfo);
|
|
|
|
|
|
|
|
val = &tree_is_expanded[finfo->tree_type];
|
|
|
|
*val = FALSE;
|
1999-12-15 07:03:11 +00:00
|
|
|
}
|
1999-03-23 03:14:46 +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
|
|
|
struct proto_tree_draw_info {
|
|
|
|
GtkCTree *ctree;
|
|
|
|
GtkCTreeNode *ctree_node;
|
|
|
|
};
|
|
|
|
|
1999-03-23 03:14:46 +00:00
|
|
|
void
|
1999-07-07 22:52:57 +00:00
|
|
|
proto_tree_draw(proto_tree *protocol_tree, GtkWidget *tree_view)
|
1999-03-23 03:14:46 +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
|
|
|
struct proto_tree_draw_info info;
|
|
|
|
|
|
|
|
info.ctree = GTK_CTREE(tree_view);
|
|
|
|
info.ctree_node = NULL;
|
|
|
|
|
|
|
|
gtk_clist_freeze ( GTK_CLIST(tree_view) );
|
|
|
|
|
1999-07-07 22:52:57 +00:00
|
|
|
g_node_children_foreach((GNode*) protocol_tree, G_TRAVERSE_ALL,
|
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_draw_node, &info);
|
|
|
|
|
|
|
|
gtk_signal_connect( GTK_OBJECT(info.ctree), "tree-expand",
|
|
|
|
(GtkSignalFunc) expand_tree, NULL );
|
|
|
|
gtk_signal_connect( GTK_OBJECT(info.ctree), "tree-collapse",
|
|
|
|
(GtkSignalFunc) collapse_tree, NULL );
|
|
|
|
|
|
|
|
gtk_clist_thaw ( GTK_CLIST(tree_view) );
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|
|
|
|
|
1999-07-07 22:52:57 +00:00
|
|
|
static void
|
|
|
|
proto_tree_draw_node(GNode *node, gpointer data)
|
1999-03-23 03:14:46 +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
|
|
|
struct proto_tree_draw_info info;
|
|
|
|
struct proto_tree_draw_info *parent_info = (struct proto_tree_draw_info*) data;
|
|
|
|
|
1999-07-07 22:52:57 +00:00
|
|
|
field_info *fi = (field_info*) (node->data);
|
|
|
|
gchar label_str[ITEM_LABEL_LENGTH];
|
|
|
|
gchar *label_ptr;
|
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
|
|
|
GtkCTreeNode *parent;
|
|
|
|
gboolean is_leaf, is_expanded;
|
1999-07-07 22:52:57 +00:00
|
|
|
|
|
|
|
if (!fi->visible)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* was a free format label produced? */
|
|
|
|
if (fi->representation) {
|
|
|
|
label_ptr = fi->representation;
|
|
|
|
}
|
|
|
|
else { /* no, make a generic label */
|
|
|
|
label_ptr = label_str;
|
|
|
|
proto_item_fill_label(fi, label_str);
|
|
|
|
}
|
1999-12-15 06:53:36 +00:00
|
|
|
|
1999-12-15 07:03:11 +00:00
|
|
|
if (g_node_n_children(node) > 0) {
|
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
|
|
|
is_leaf = FALSE;
|
|
|
|
if (tree_is_expanded[fi->tree_type]) {
|
|
|
|
is_expanded = TRUE;
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
is_expanded = FALSE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
is_leaf = TRUE;
|
|
|
|
is_expanded = FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
info.ctree = parent_info->ctree;
|
|
|
|
parent = gtk_ctree_insert_node ( info.ctree, parent_info->ctree_node, NULL,
|
|
|
|
&label_ptr, 5, NULL, NULL, NULL, NULL,
|
|
|
|
is_leaf, is_expanded );
|
|
|
|
|
|
|
|
gtk_ctree_node_set_row_data( GTK_CTREE(info.ctree), parent, fi );
|
1999-07-07 22:52:57 +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
|
|
|
if (!is_leaf) {
|
|
|
|
info.ctree_node = parent;
|
1999-07-07 22:52:57 +00:00
|
|
|
g_node_children_foreach(node, G_TRAVERSE_ALL,
|
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_draw_node, &info);
|
1999-07-07 22:52:57 +00:00
|
|
|
}
|
1999-03-23 03:14:46 +00:00
|
|
|
}
|