On Mon, Feb 23, 2009 at 5:06 PM, Stig Bjørlykke
<stig@xxxxxxxxxxxxx> wrote:
2009/2/23 Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>:
> (1) Common channel counters at the top. This should be a fixed-sized table
> with just one row where common channel counters are displayed. 2 rows (one
> for BCH and one for PCH) might be nicer, but I'd still want a fixed size).
Do you really want this data in a table?
Why not just add this fields as labels, like on the top of the
Statistics->Summary window?
It doesn't really have to be a table, I just wanted the fields to appear in a similar way in all places.
> (2) Per-UE (User Equipment) data, where each row shows high-level details
> counters for that UE (and where the first column, RNTI, is the key). This
> table can have lots of rows, and they should be scrolled. When the whole
> window is stretched vertically, I'd like this area to expand and the other
> parts to maintain their fixed sizes
Have a look at the "WLAN Traffic" code (wlan_stat_dlg.c) where the "%
Packets" column expands, and the table is scrollable.
I did look at this file, and will look at it more closely again. I noticed that you were creating a pane with a splitter, which I didn't want as there is only one non-fixed sized part of the window.
> (3) Single UE counters in more detail. i.e. more details about the UE that
> is currently selected in (2). This should have 4 fixed rows.
Maybe like in (1) with fixed labels?
It could be, yes, and that would probably be neater.
Do you have a capture file?
I'll send it to you directly, because of its size. Not very interesting, except that it has a few UEs and they don't have quite the same SDU counts. I'll get a better one and put it on the wiki later on.
Thanks,
Martin
--
Stig Bjørlykke
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
