Comment # 4
on bug 10159
from Guy Harris
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > VALS() should be usable - define two separate hf_ values, with the *same*
> > > field name, and with *different* value_string tables, and use the
> > > appropriate one based on the subtype.
> >
> > This was one of the solutions proposed. This creates problems with "Unknown"
> > type, no particular hf is correct there, had to resort to simply add_text,
> > which is no longer navigable.
>
> Presumably by ""Unknown" type" you mean "a subtype for which there's no
> correct value_string table"; if so, then create an hf_ with an *empty*
> value_string table, so that *everything* shows up as "Unknown".
Or create an hf_ with *no* value_string table.
You are receiving this mail because:
- You are watching all bug changes.