https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16498
--- Comment #8 from Peter Wu <pe...@lekensteyn.nl> ---
Good point about the sharing aspect. So overloading the name it is.
What about using ` // ` (space, two forward slashes, space) as separator? This
would avoid ambiguities in case people try to use a name such as `https://`.
And to completely resolve any other ambiguity, treat any string with that
prefix as the non-grouped variant:
- `TCP` -> no group, name `TCP`
- `TCP // Ack` -> group `TCP`, name `Ack`
- `TCP//Ack` -> no group, name `TCP//Ack` (spaces are important)
- ` // X` -> no group, name `X`
- ` // X // Y` -> no group, name `X // Y`
- `// X` -> no group, name `X` (spaces are important)
Two weird edge cases that should probably be rejected, but are still accepted
at the moment:
- (empty string) -> no group, no name
- `X // ` -> group `X`, no name (for consistency)
I think a tree view with group nodes and children would look nicer, but you are
right that would require additional tracking. Especially since the tree view
order may not 1:1 match the UAT model. For example, consider these names:
A // 1
4
A // 2
B // 5
A // 3
which might look better as:
A
1
2
3
4
B
5
Once the storage format is well-defined, this view issue could be treated
later.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
