diff options
| author | Guy Harris <guy@alum.mit.edu> | 2015-12-31 17:12:15 -0800 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2016-01-01 01:12:56 +0000 |
| commit | aaa5ed4ad73ca537e3cd1a45ce7b8bb10371b822 (patch) | |
| tree | 4d59502ab97968e67ac05c140b0ebcf0259de15f /ui/gtk/packet_panes.c | |
| parent | 44eda0c64e7365196aed5f2166b33baaac16a45f (diff) | |
No, you don't have to allocate colors.
That code's been unused since at least 1.12, so apparently it's not
needed. To the extent that it needs to be allocated at all - which is
the case only if a colormap is being used - it's apparently all done
under the covers.
Change-Id: Ib25bfba618b0af4a60ce991a974de1e3f2f89158
Reviewed-on: https://code.wireshark.org/review/12981
Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'ui/gtk/packet_panes.c')
| -rw-r--r-- | ui/gtk/packet_panes.c | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/ui/gtk/packet_panes.c b/ui/gtk/packet_panes.c index 241292b0cc..128c71555a 100644 --- a/ui/gtk/packet_panes.c +++ b/ui/gtk/packet_panes.c @@ -1146,14 +1146,6 @@ void proto_draw_colors_init(void) if(colors_ok) { return; } -#if 0 - /* Allocating collor isn't necessary? */ - get_color(&expert_color_chat); - get_color(&expert_color_note); - get_color(&expert_color_warn); - get_color(&expert_color_error); - get_color(&expert_color_foreground); -#endif expert_color_comment_str = gdk_color_to_string(&expert_color_comment); expert_color_chat_str = gdk_color_to_string(&expert_color_chat); expert_color_note_str = gdk_color_to_string(&expert_color_note); @@ -1161,9 +1153,6 @@ void proto_draw_colors_init(void) expert_color_error_str = gdk_color_to_string(&expert_color_error); expert_color_foreground_str = gdk_color_to_string(&expert_color_foreground); -#if 0 - get_color(&hidden_proto_item); -#endif colors_ok = TRUE; } |