On 21/02/15 05:56, Thiago Macieira wrote:
> On Saturday 21 February 2015 04:34:07 Nikos Chantziaras wrote:
>> is there a way to detect at runtime whether Qt has glib support?
>> Right now I'm simply assuming that all Linux users have a Qt built
>> with "-glib" (so in that case a glib event loop is
True. This important part did my quick grep not show. :-)
Now I have to figure out where the qtlogging.ini came from. :-/
Guido
On Sat, 21 Feb 2015 11:48:42 +
Richard Moore wrote:
> On 21 February 2015 at 11:12, Guido Seifert wrote:
>
> > I doubt your explanation. :-)
> > Reason 1: When I
On 21 February 2015 at 11:12, Guido Seifert wrote:
> I doubt your explanation. :-)
> Reason 1: When I discovered this, I did not have a qtlogging.ini anywhere
> in my system.
> Reason 2:
>
> > qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:
> qDebug("xcb: moved mouse to %4d, %4d; button stat
I doubt your explanation. :-)
Reason 1: When I discovered this, I did not have a qtlogging.ini anywhere in my
system.
Reason 2:
> qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:
> qDebug("xcb: moved mouse to %4d, %4d; button state %X", mev->event_x,
> mev->event_y, static_ca
To be seeing this, you must have turned on qt.qpa.input categorized logging.
You need to get used to managing your qtlogging.ini depending on what you are
trying to debug. (And I think we should write some sort of tool to manage it,
because there are a lot of categories now.) Maybe logging mo
