Wireshark · Wireshark-dev: Re: [Wireshark-dev] Warnings when loading preferences

[mmann78@xxxxxxxxxxxx]

Technically the prefences aren't "obsolete", they are just renamed for (internally) optimized code.  Should the "old names" still be noted as such in a current preferences file?  The main reason for the new "optimized" code was to get the "general" preferences to use the "preference API", like all of the protocol preferences are (so it would be open to being called "obsolete" in the future).  That's why supporting this "backwards compatibility" to the old names of the "general preferences" will make the code look a little ugly, but is certainly acheivable.

 

-----Original Message-----
From: Stig Bjørlykke <stig@xxxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Wed, Aug 1, 2012 9:12 am
Subject: Re: [Wireshark-dev] Warnings when loading preferences

On Wed, Aug 1, 2012 at 2:50 PM, Anders Broman
<anders.broman@xxxxxxxxxxxx> wrote:
> Is it worth it when you can just resave your preferences?

The user may have several profiles with different settings, and will
have to update all profiles with new settings again.
I think we should try preserving the preferences instead of giving warnings.

We also mark removed dissector preferences
(prefs_register_obsolete_preference) and protocols
(prefs_register_protocol_obsolete) as obsolete.


-- 
Stig Bjørlykke
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe