Wireshark mailing list archives
Re: new dissector - dynamic value string table?
From: Max Baker <max () warped org>
Date: Tue, 26 Feb 2013 19:37:23 -0800
On 2/26/2013 6:51 PM, Guy Harris wrote:
On Feb 26, 2013, at 6:37 PM, Max Baker <max () warped org> wrote:The problem I have now is I have different possible values for a value_string list, but they are data-dependent.Why not have multiple value_string lists, then?
Hi Guy, Good question. My example was a bit contrived -- but about 90% of any given list is common to all cameras that support PTP. The last 10% is device-specific. Ideally I just want a way to dynamically add-on the last 10% depending on model. -m ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- new dissector - dynamic value string table? Max Baker (Feb 26)
- Re: new dissector - dynamic value string table? Guy Harris (Feb 26)
- Re: new dissector - dynamic value string table? Max Baker (Feb 26)
- Message not available
- Re: new dissector - dynamic value string table? Max Baker (Feb 27)
- Re: new dissector - dynamic value string table? Michal.Labedzki (Feb 28)
- Re: new dissector - dynamic value string table? Max Baker (Feb 28)
- Re: new dissector - dynamic value string table? Jakub Zawadzki (Feb 28)
- Re: new dissector - dynamic value string table? Max Baker (Feb 26)
- Re: new dissector - dynamic value string table? Guy Harris (Feb 26)
- Re: new dissector - dynamic value string table? Max Baker (Feb 27)