On Tue, Mar 8, 2011 at 9:02 PM, Chris Maynard <chris.mayn...@gtech.com> 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.
I think this sort of warnings are important to an user trying to configure the installed version of Wireshark (which usually is only one) with some custom configurations, because he/she may not be able to spot an error if not given a warning. They are less important to developers/advanced users having multiple instances of Wireshark, because we know what we are doing (well, most of the time). My personal opinion is that we should focus on the user (give warnings), but have an option for developers/advanced users to disable warnings window(s). Maybe display all warnings (fetched from statusbar_push_temporary_msg?) in one window at startup, with an option to disable? This window can also be available from the menu for later analysis of all warnings. -- Stig Bjørlykke ___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe
