summaryrefslogtreecommitdiff
path: root/ui/tap-tcp-stream.h
diff options
context:
space:
mode:
authorGerald Combs <gerald@wireshark.org>2013-08-30 21:15:24 +0000
committerGerald Combs <gerald@wireshark.org>2013-08-30 21:15:24 +0000
commit1d27c70838a8dd04dc302dc6c6527bb852b58cc5 (patch)
tree3940900b523269602e861776613d3568bb59f188 /ui/tap-tcp-stream.h
parent8445c81d50c9c49b61298eed974dbe9f0ed1826c (diff)
downloadwireshark-1d27c70838a8dd04dc302dc6c6527bb852b58cc5.tar.gz
Add an item tracer to the TCP stream graph. Enable packet selection.
QCustomPlot data sets are made up of keys (x axis by default) and values (y axis). It looks like we can have multiple values for a given key (i.e. we can show multiple sequence numbers for a given timestamp) but QCPItemTracers can only be positioned by a key and not a key+value pair. This makes our graph selection behavior a bit different compared to the GTK+ version. We can only select one segment for a give timestamp but our selection targets are much larger (the height of the graph). Add a map for segment data so we don't have to iterate to find them. Use UTF8_RIGHTWARDS_ARROW where appropriate. Set a window title. Tell the user what will happen if he or she clicks. Disable graph selection. svn path=/trunk/; revision=51604
Diffstat (limited to 'ui/tap-tcp-stream.h')
-rw-r--r--ui/tap-tcp-stream.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/ui/tap-tcp-stream.h b/ui/tap-tcp-stream.h
index a502354daa..71f9a5c0f6 100644
--- a/ui/tap-tcp-stream.h
+++ b/ui/tap-tcp-stream.h
@@ -70,6 +70,7 @@ struct tcp_graph {
guint16 src_port;
address dst_address;
guint16 dst_port;
+ /* Should this be a map or tree instead? */
struct segment *segments;
};