On Sunday, 27 September 2020 22:08:53 PDT Rainer Wiesenfarth wrote:
> I found a workaround in our code by removing a call to
> QCoreApplication::processEvents() and reorganizing some code.
Remove all of them. Everywhere you're using them, they're wrong.
The best solution is to replace them with a
Hi all,
thanks for your assistance and hints!
I found a workaround in our code by removing a call to
QCoreApplication::processEvents() and reorganizing some code.
Concerning your suggestions:
- I can exclude not properly registered metatypes, as all signals are of
type "void signal()"
No. Have neither time nor willing to create one...
I don't believe it's not a wide spread case. But even if not - have no
willing for this for now, sorry...
On 9/26/2020 6:47 PM, Giuseppe D'Angelo wrote:
On 26/09/2020 16:48, Alexander Dyagilev wrote:
I'm not sure what you mean exactly, but I'
Well, let me not to use it please, i want my app to continue to work lol.
On 9/26/2020 6:43 PM, Thiago Macieira wrote:
On Saturday, 26 September 2020 07:53:23 PDT Alexander Dyagilev wrote:
template
inline void qRegisterMyMetaType(const char *name)
{
if (QMetaType::type(name) == QMetaType
On 26/09/2020 16:53, Alexander Dyagilev wrote:
I use this helper macro for this (register a metatype in runtime):
template
inline void qRegisterMyMetaType(const char *name)
{
if (QMetaType::type(name) == QMetaType::UnknownType)
qRegisterMetaType(name);
}
#define Q_REGISTER_MY_MET
On 26/09/2020 16:48, Alexander Dyagilev wrote:
I'm not sure what you mean exactly, but I've seen many such situations
(when connection did not work because metatype was not registered) and
never saw any warnings anywhere.
I mean that when you do a queued connection or a queued activation and
On Saturday, 26 September 2020 07:53:23 PDT Alexander Dyagilev wrote:
> template
> inline void qRegisterMyMetaType(const char *name)
> {
> if (QMetaType::type(name) == QMetaType::UnknownType)
> qRegisterMetaType(name);
> }
Better implementation:
template
inline void qRegisterMyMet
I use this helper macro for this (register a metatype in runtime):
template
inline void qRegisterMyMetaType(const char *name)
{
if (QMetaType::type(name) == QMetaType::UnknownType)
qRegisterMetaType(name);
}
#define Q_REGISTER_MY_METATYPE(type) qRegisterMyMetaType(#type);
Usage ex
I'm not sure what you mean exactly, but I've seen many such situations
(when connection did not work because metatype was not registered) and
never saw any warnings anywhere.
On 9/26/2020 12:02 PM, Giuseppe D'Angelo via Interest wrote:
Il 26/09/20 07:55, Alexander Dyagilev ha scritto:
Yeah, i
> On 25 Sep 2020, at 21:26, Giuseppe D'Angelo via Interest
> wrote:
>
> Il 24/09/20 17:55, Rainer Wiesenfarth ha scritto:
>> - if I take the application built and running without this issue with Qt
>> 5.12.5 and replace the DLLs with those from Qt 5.15.0, the issue appears.
>> That means there
Il 26/09/20 07:55, Alexander Dyagilev ha scritto:
Yeah, it's possible that some metatype (used in signal) is registered in
Qt 5.12 and is NOT registered in Qt 5.15, thus connection does not work
between objects in different threads.
It's required to register it manually then.
Do you know of a
Hello,
Yeah, it's possible that some metatype (used in signal) is registered in
Qt 5.12 and is NOT registered in Qt 5.15, thus connection does not work
between objects in different threads.
It's required to register it manually then.
On 9/26/2020 12:31 AM, Harri Porten wrote:
Hello Rainer,
Hello Rainer,
On Thu, 24 Sep 2020, Rainer Wiesenfarth wrote:
I have a strange problem that for a certain queued signal/slot
connection the signal is emitted, but the event does not reach the
connected slot. This problem is reproducible in Qt 5.15.0, but does not
occur in Qt 5.12.5. Unfortunat
Il 24/09/20 17:55, Rainer Wiesenfarth ha scritto:
- if I take the application built and running without this issue with Qt
5.12.5 and replace the DLLs with those from Qt 5.15.0, the issue
appears. That means there is a change in the event handling between
5.12.5 and 5.15.0 that causes the issue
Hi all,
the topic is Qt on Windows, versions 5.15.0 vs. 5.12.5, connections made
with Qt::QueuedConnection, event loop of a worker thread.
I have a strange problem that for a certain queued signal/slot connection
the signal is emitted, but the event does not reach the connected slot.
This problem
15 matches
Mail list logo
