Re: Compiling with or without extcap

[Roland Knall <rknall () gmail com>]

Still, it looks for possible new extcap programs, which slows down the
systems a little bit I guess. But beside that, Dario is right, if you
disable all extcap, it behaves as if no extcap was present.



On Thu, Jan 4, 2018 at 3:21 PM, Dario Lombardo <dario.lombardo.ml () gmail com>
wrote:

> On Thu, Jan 4, 2018 at 3:10 PM, Anders Broman <anders.broman () ericsson com>
> wrote:
>
> > I don’t have a problem with making extcap a mandatory feature of
> > Wireshark. But since extcap prolongs the startup time and clutters the
> > interface list.
> >
> > I would like a feature to turn some or all extcap interfaces off. I think
> > it’s good to have them default available to make it obvious they exist but
> > none of the default ones are particularly useful to me.
>
> This is related to user experience, not compilation. Did you try to
> disable some interfaces group, main window, next to the filter? There is
> wired, wireless, USB and external interfaces. Disable the last one and you
> get rid of all extcaps (display only).
>
> ____________________________________________________________
> _______________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org?subject=
> unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe