Chris Maynard wrote:
I regularly switch between a custom build of Wireshark for analyzing my
company's protocols and the trunk when doing general Wireshark
development/testing. Unfortunately, I have lots of custom color filters in
place that are invalid for the trunk for obvious reasons. But every time I
switch to the trunk, for every custom color filter I have, I get an annoying
dialog telling me, "Could not compile color filter "blah" from saved filters."
I've made a change in my local sandbox to avoid this, but would anyone have any
grumblings if I permanently eliminate that dialog? Here's all I do to get rid
of it:
I don't mind.
What about spewing a warning to stdout like we do when we find a
preference we don't know/understand? (Just so there's _some_ log of the
"failure".)
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
