Comment # 5
on bug 10159
from Anish Bhatt
> 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".
Yes, that's what I meant. But now we have 3 hf_'s, an optional val_string and
requisite code to display 4 strings and an unknown. The unknown itself could
have variations. That seems like a lot of code addition for a simple problem.
If I can use VALS() to display a string equivalent for a bitmask, surely the
option to use a custom string instead is not too much to ask ?
You are receiving this mail because:
- You are watching all bug changes.