General and Desktop

@Christian-Ehrlicher

Pardon me, but how do I make sure to compile in release? If I set CMAKE_BUILD_TYPE to Release, the issue stays the same

Start from the example in https://doc.qt.io/qt-6/qproxystyle.html#details and see what happens.

@jsulm said in Cannot determine dependencies of qtposition_nmea.dll:

@davecotter I'm wondering why qtposition_nmea.dll should depend on Qt6SerialPort?! Strange.

i wonder the same.
also why does it depend on QtQuick?

@GrecKo said in QSignalSpy verify emission order:

You don't have to use QSignalSpy, you could store the received signals in an ordered list:

QStringList receivedSignals; QObject::connect(&inst, &MyClass::started, &inst, [&] { receivedSignals.append("started"); }); QObject::connect(&inst, &MyClass::finished, &inst, [&] { receivedSignals.append("finished"); }); inst.doSomething(); QStringList expectedSignals = {"started", "finished"}; QCOMPARE(receivedSignals, expectedSignals);

That makes sense. I figured that using an external mechanism would do the trick, though your idea with a lambda populating a QStringList is far simpler than what I was cooking up. I was hoping for a simple solution, and this looks like it'll be the simplest way of achieving my goal.

Thanks!

I entered the following code and it didn't do anything.

soReport->setResizeMode(QListWidget::Adjust);

Oh yes, thank you. That was a total thinking failure. What I actually wanted to test was something like that:

{ Nix nix4(4, "Hello, I'm four"); *nix1 = nix4; } qWarning() << "nix1: " << nix1->display(4);

And that works.

*nix2 = *nix1; delete nix1

works too

Thanks, solved!

Any new on how to solve the problem

@shavera said in Is there a canonical way to set up QApplication and Google Test together?:

After many iterations, I've finally found what I think works well here:

int main(int argc, char *argv[]) { QCoreApplication app{argc, argv}; QTimer::singleShot(0, [&]() { ::testing::InitGoogleTest(&argc, argv); auto testResult = RUN_ALL_TESTS(); app.exit(testResult); }); return app.exec(); }

it works for me

@nyaruko said in Qt warning of type conversion already registered:

I have a multi-thread Qt program...

This is a common cause of issues of all flavours. It may be as simple as the same setup code for shared configuration, e.g. the metatype database, executing in multiple threads.

@ocgltd said in Qt warning of type conversion already registered:

Any way to track this down?

You could provide a minimal program that invokes the message, some basic Qt version information, tool chain information, etc. Something that happens twice in ten years here and spans many Qt versions is not likely to have an immediate, "I've seen that before," response.

I am not sure to understand your phrase correctly.

So the rule is: if you create a QWidget subclass where you want to use style sheets, then it needs both the Q_OBJECT macro and the paintEvent reimplementation.

@Christian-Ehrlicher Thank you, I figured it out, using opt->rect's x and y attributes draws it in the correct place.

You are not linking against the library you are testing.

workaround: Add Qt::NoTitleBarBackgroundHint window flag

@SGaist I am on windows.

@Mark81
It is "difficult" because you do not have a proper foreign key relation, which is what QSqlRelationalTableModel requires. Having some other column (eventType) whose value dictates which of multiple tables (alarms, sessions, ...) is the foreign one in which to look up the key column's value is supported neither in SQL nor Qt's QSqlRelationalTableModel --- it is not allowed in the definition of a foreign key.

Either think about redefining/rearchitecting your intended relationships which fits better with SQL or (in my opinion) give up trying to use QSqlRelationalTableModel. Instead read in the contents of all required/linked tables into their own normal QSqlTableModels, as well as the original "source" table, and implement your desired logic yourself in client code as required for your desired behaviour.

@nicker-player

Set a stylesheet?!