lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] 004e:err:tooltips:TOOLTIPS_Timer How did this happen?


From: Vadim Zeitlin
Subject: Re: [lmi] 004e:err:tooltips:TOOLTIPS_Timer How did this happen?
Date: Wed, 28 Mar 2018 02:58:30 +0200

On Tue, 27 Mar 2018 22:23:13 +0000 Greg Chicares <address@hidden> wrote:

GC> Below I attach a complete log of a 'wx_test' run, just in case that's
GC> helpful somehow, but the only interesting thing I notice is the seven
GC> occurrences of:
GC>   004e:err:tooltips:TOOLTIPS_Timer How did this happen?
GC> If no one else sees this without 'wine', I'll just dismiss it as yet
GC> another 'wine' oddity.

 Well, it's definitely a Wine message (see
https://github.com/wine-mirror/wine/blob/0a72708126f5b8fc06698172d973bb529944c3bf/dlls/comctl32/tooltips.c#L2081
for where it's given in its sources), so it definitely can't be seen when
not running Wine. But it could still indicate that we're doing something
wrong, e.g. forgetting to relay some message to the tooltip. However I
don't really see anything wrong in wxMSW code and I suspect that perhaps
Wine code just doesn't deal with the automated testing scenario in which
some messages are generated much faster than usual (the expiration delay
for this timer is 40ms which is a really long time when events are being
simulated programmatically...).

 Perhaps enabling tracing of of the messages in the "tooltips" category
could provide some more information. Or I could (finally, I've been
planning to do it since quite some time) build my own Wine and debug it,
if you think it's worth doing this.

 Regards,
VZ


reply via email to

[Prev in Thread] Current Thread [Next in Thread]