Wireshark-bugs: [Wireshark-bugs] [Bug 4558] "Expand subtrees" doesn't work for "new" subtrees
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4558
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jeff.morriss.ws@xxxxxxxxx
Resolution| |WONTFIX
--- Comment #1 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-03-24 07:37:15 PDT ---
Well, this is more or less intentional.
Each dissector has some number of "ett" variables: one for each sub-tree. Some
dissector writers use just one variable so the result is that expanding one
subtree in one packet means that moving to another packet results in *all*
subtrees being expanded. Personally I don't like that behavior and would much
rather there be multiple ett variables and thus multiple subtrees.
The DNS dissector has several ett variables, including one for queries and one
for answers. When you expanded all the subtrees in the query, the "query"
subtree got expanded but (of course) the "answer" tree was not. Moving to the
answer packet meant that (only) the trees that were expanded in the query
packet got expanded.
Part of the reason I like behavior like this is that I may be interested in the
details of, say, the queries but I only want the top-of-the-subtree summary of
the answers. When I move around from packet to packet the subtree expansions
stay the same for each kind of packet.
Closing this one as WONTFIX for this reason.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
