On Sun, Jul 22, 2018 at 7:08 PM, Sérgio Martins wrote:
>
> For statistics you probably want to use tracepoints [1].
[1] http://lists.qt-project.org/pipermail/development/
> 2017-February/028762.html
>
On Sun, Jul 22, 2018 at 8:13 PM, Giuseppe D'Angelo via Interest <
interest@qt-project.org>
On Sunday, 22 July 2018 09:01:02 PDT Konstantin Shegunov wrote:
> On Sun, Jul 22, 2018 at 6:54 PM, Thiago Macieira
> wrote:
> > QCoreApplication::notify will help you for now, but that will not work in
> > Qt
> > 6.
>
> Yes, I read the warning, that's why I posted here. My follow up question(s)
Il 22/07/2018 18:08, Sérgio Martins ha scritto:
For statistics you probably want to use tracepoints [1].
[1]http://lists.qt-project.org/pipermail/development/2017-February/028762.html
And in particular this patch:
https://codereview.qt-project.org/#/c/229165/
HTH,
--
Giuseppe D'Angelo |
On Sun, Jul 22, 2018 at 11:26 AM, Konstantin Shegunov
wrote:
> Hello,
> Is there any way to inspect an event that was delivered, just after the
> fact? Looking at the source it seems the only way to do this is to have
> QObject::event or QCoreApplication::notify overridden, is that correct?
>
>
On Sun, Jul 22, 2018 at 6:54 PM, Thiago Macieira
wrote:
>
> QCoreApplication::notify will help you for now, but that will not work in
> Qt
> 6.
>
Yes, I read the warning, that's why I posted here. My follow up question(s)
would then be:
How will the fine grained control that notify() gives be
On Sunday, 22 July 2018 08:43:10 PDT Konstantin Shegunov wrote:
> On Sun, Jul 22, 2018 at 6:36 PM, Thiago Macieira
> wrote:
> > If you only need this for a particular class,
>
> Unfortunately no, not for a particular class. Ideally I'd use something
> like an event filter that'd be triggered
On Sun, Jul 22, 2018 at 6:36 PM, Thiago Macieira
wrote:
>
> If you only need this for a particular class,
Unfortunately no, not for a particular class. Ideally I'd use something
like an event filter that'd be triggered after the event was delivered, but
I'm not aware of any such functionality.
On Sunday, 22 July 2018 03:26:30 PDT Konstantin Shegunov wrote:
> Is there any way to inspect an event that was delivered, just after the
> fact? Looking at the source it seems the only way to do this is to have
> QObject::event or QCoreApplication::notify overridden, is that correct?
If you only
Hello,
Is there any way to inspect an event that was delivered, just after the
fact? Looking at the source it seems the only way to do this is to have
QObject::event or QCoreApplication::notify overridden, is that correct?
I'm interested in QEvent::MetaCall specifically. I want to collect some
