Similar question for the 'experts' and 'last_expert' GLists in the
expert_module struct.

Evan

On Sat, Jul 6, 2013 at 8:23 AM, Evan Huus <[email protected]> wrote:
> Are there plans to use the expert_modules tree added by this commit? I
> was looking at switching it to wmem but realized that it's never
> actually used for lookups...
>
> Evan
>
> On Fri, May 24, 2013 at 1:59 PM,  <[email protected]> wrote:
>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=49559
>>
>> User: mmann
>> Date: 2013/05/24 10:59 AM
>>
>> Log:
>>  Add expert info configuration framework.  Bug 2412 
>> (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2412).
>>
>>  Expert info "fields" can now be registered/addressed by name.  Right now, 
>> the basic framework allows expert info fields to become "display filters".  
>> However more could be done, like user preferences overriding default 
>> severity level, speeding up expert info dialog load time by not needing to 
>> redissect a file, etc.
>>
>>  Long term goal is to have all expert_info filterable and have the 
>> functionality of expert_add_info_format() include the "registered index".  
>> expert_add_info_format_text() is the workaround until all current calls to 
>> expert_add_info_format() have been updated with either expert_add_info() or 
>> expert_add_info_format_text().  Then the remaining 
>> expert_add_info_format_text() will be renamed to expert_add_info_format().
>>
>> Directory: /trunk/epan/
>>   Changes    Path          Action
>>   +3 -1      epan.c        Modified
>>   +194 -7    expert.c      Modified
>>   +77 -0     expert.h      Modified
>>   +2 -2      packet.c      Modified
>>   +1 -1      proto.c       Modified
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-commits mailing list <[email protected]>
>> Archives:    http://www.wireshark.org/lists/wireshark-commits
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
>>              
>> mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________
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

Reply via email to