Comment # 5
on bug 6357
from Guy Harris
(In reply to comment #4)
> I'm not sure in which way you mean that question. It doesn't require they
> be "visible" in the literal sense of visible through the GUI, but Lua can
> only access field_info's from the proto_tree if the field_info is actually
> created/populated, of course. Since they're usually *not* populated, and
> only fully populated when the tree is "visible" (in the GUI sense), then I
> suppose you could say Lua can only use visible ones.
That sounds like a bug. "Visible" in the GUI sense should only govern whether
the field shows up in the packet-details pane and in text output from "tshark
-V" and "Export Packet Dissection -> As "Plain Text" file" and "...As
"Postscript" file". Fields that are "visible" in the GUI sense may have to be
put into the protocol tree, but "invisible" fields (e.g., ip.addr) need at
least to be available for "-e" and "...As XML - "PDML" (Packet details) file".
In addition, "visible", at least for "tshark -V" and "...As "Plain Text" file"
and "...As "Postscript" file", requires that the "representation", i.e. what's
displayed to users, be filled in, but just getting the *value* doesn't.
So perhaps "visible" controls too much, and there should be more than one
attribute to control what's populated.
You are receiving this mail because:
- You are watching all bug changes.