FWIW, I'm working a little bit towards refactoring the preference
functionality. Nothing big, just trying to encapsulate all functionality into
the prefs.c file (it's mostly the memory management issues that I want to
simplify for (code) users of the preference interface).
I'm not sure if this would make any design related to this easier, I just
wanted to put it out there to minimize potential merge issues.
-----Original Message-----
From: Anders Broman <[email protected]>
To: wireshark-dev <[email protected]>
Sent: Thu, Jan 5, 2017 10:30 am
Subject: [Wireshark-dev] Preferences needed during Wireshark startup
Hi,
Looking into the time required to start Wireshark I came across a problem with
the console on Windows where the preferences
prefs.console_log_level
prefs.gui_console_open
is needed for logging to work but preferences are set pretty late in the
startup phases as dissectors etc need to have their preferences loaded first.
I’m also thinking about adding preferences for loading extcap plugins or not
which would make it easier to “activate” them when needed and perhaps chose
Which ones one like to use. But those preferences would be needed before the
preference file is loaded currently.
One possible solution could be to load and parse the file into a structure for
later processing early in the startup and then “look” at the list of preferences
When needed during startup or create a new file with “basic preferences” loaded
early or…
I’m not sure I’m up to taking on this task but at least we could discuss design
ideas and if some one is willing to take it on I’d be grateful.
Best regards
Anders
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
