Wireshark-dev: Re: [Wireshark-dev] RTP player - a suggestion
Roland, Who are you asking? :-P I have plenty of captures handy, but it would probably be best if I record some new ones to illustrate the problems more clearly. I could also write up a “steps to reproduce” showing how I would normally do things in the v1 GUI, and how the v2 GUI makes it harder or impossible to do the same thing. Should I just reply with the files attached (and zipped?), or is there a better way to submit captures? ~Peter From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Roland Knall Could you provide some sample captures about the RTP issues cheers On Tue, May 2, 2017 at 6:58 PM, Erik de Jong <erikdejong@xxxxxxxxx> wrote: On Tue, Mar 28, 2017 at 9:44 AM, Alexis La Goutte <alexis.lagoutte@xxxxxxxxx> wrote: On Mon, Mar 27, 2017 at 9:33 PM, Jirka Novak <j.novak@xxxxxxxxxxxx> wrote: Hi, For me, it can be a valid approach because we can to remove GTK... (in next release GTK is disable by default and i think for 2018, we remove GTK support...) I'm afraid this thread kind of silently died, looks like it's a difficult thing to tackle ;-) In my opinion my suggestion earlier (https://www.wireshark.org/lists/wireshark-dev/201703/msg00073.html) is the least invasive way to go about this. It won't harm legacy users and will promote code reuse. |
- Follow-Ups:
- Re: [Wireshark-dev] RTP player - a suggestion
- From: Guy Harris
- Re: [Wireshark-dev] RTP player - a suggestion
- References:
- Re: [Wireshark-dev] RTP player - a suggestion
- From: Roland Knall
- Re: [Wireshark-dev] RTP player - a suggestion
- Prev by Date: Re: [Wireshark-dev] RTP player - a suggestion
- Next by Date: Re: [Wireshark-dev] RTP player - a suggestion
- Previous by thread: Re: [Wireshark-dev] RTP player - a suggestion
- Next by thread: Re: [Wireshark-dev] RTP player - a suggestion
- Index(es):
- Get Wireshark
- Download
- Code of Conduct