Guy Harris wrote:
> One feature that might be useful would be support for a "Wireshark
> settings file" that could be associated with a capture, so that if a
> file named foo.{pcap,cap,...} were opened, Wireshark could look for
> foo.wssettings, or something such as that, and, if it finds, load
> it.
Saving setting based on just the file name would not work for me, as I
often have files with the same name but different settings. The files
end up in different directories.
>> Or is the suggestion on the Wiki that profiles could be
>> implemented as sub-directories of the user's settings directory
>> better? That would mean profiles could be applied to different
>> files and different live captures.
That seems better, but a bit more complicated.
Its probably a bit soon to go into detail, but I had a look at
gtk/decode_as_dlg.c to see what it would take to just save the settings.
I was thinking I could add save & load buttons to the Alalyze/User
Specified Decode... dialog. I haven't done any Wireshark development
other than some dissectors, but it does not seem too difficult.
I think having two sets of settings would be useful. Global ones saved
under Edit->Preferences and per-file ones. Guess the trick would be not
having the per-file ones saved over the top of the file specific ones.
Thanks,
Andy
_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev
