Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Checking for Qt in a dissector

From: Roland Knall <rknall@xxxxxxxxx>
Date: Tue, 4 Jul 2017 11:12:19 +0200
Hi Paul

I know what you want to achieve, but I really think this way around it is a very bad idea (as I mentioned in the past). The plugin-dissector code still runs in the epan context, and there it does not have a Qt reference it can apply for. 

The GUI part of the plugin is another question, but for that you find the code in the pluginifdemo, where the selection is taking place in the uihandler wrapper, which has to decide if it should create a QApplication context or reuse Wiresharks context. 

cheers,
Roland

On Tue, Jul 4, 2017 at 12:11 AM, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:
It's registering as a dissector but it doesn't add to the tree or anything like that.  It's for the Syncro project I'm working on; as per Gerrit, although I have completely rewritten the code since the last patch set.

Sent from Samsung Mobile on O2


-------- Original message --------
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: 03/07/2017 19:25 (GMT+00:00)
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Checking for Qt in a dissector

On Jul 3, 2017, at 10:22 AM, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:

> That won't work in this case.  It's actually a plugin rather than a true dissector - I didn't describe it well.

"Plugin" and "true dissector" aren't opposite.  Did you mean "post-dissector" rather than "plugin", as in "it's a plugin post-dissector"?

> It uses Qt code so it definitely will only work with Wireshark 2.x.x.

Perhaps we need to have separate directories for plugins that contain GUI code and plugins that don't.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
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

______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
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