General and Desktop

@Will said in Radio button circle becomes colored in when using a scroll area Qt6 on Windows:

Question 1: Is this normal / expected?

Yes since it's the windows 11 style

Question 2: Can this be turned off?

Yes, use the windowsvista style: https://doc.qt.io/qt-6/qstyle.html#setting-a-style

Ok. is it ok if I post a screenshot of MainMenu here ?

Hi and welcome to devnet,

Intriguing issue ! I would recommend bringing it to the interest mailing list. You'll find there Qt developers/maintainers. This forum is more user oriented.

@petterPan said in Background of Icon on a QPushButton:

you can do this by using QSS

Yes, see the documentation: https://doc.qt.io/qt-6/stylesheet-examples.html#customizing-qpushbutton
For the different states you can use the pseudo states described here: https://doc.qt.io/qt-6/stylesheet-reference.html#checked-ps

Thanks for the message @jsulm & @Christian-Ehrlicher

Turns out, that I'm just too stupid :-) macos builds have been renamed to "Desktop".

The correct solution in my scenario is to install an event filter.

void SplashScreenListModel::append(const QString& name, QObject* item) { // Get dynamic property initialized value // If the returned variant is invalid, the property is not set yet QVariant v = item->property("initialized"); bool initStatus = false; if (v.isValid() && v.value<bool>()) initStatus = true; s_instance->beginInsertRows(QModelIndex(), s_instance->m_data.length(), s_instance->m_data.length()); s_instance->m_data.append(SPDataItem(name, item, initStatus)); s_instance->endInsertRows(); // Set name for identification in slot item->setObjectName(name); // Install eventfilter item->installEventFilter(s_instance.get()); } bool SplashScreenListModel::eventFilter(QObject* obj, QEvent* event) { if (event->type() != QEvent::DynamicPropertyChange) return QObject::eventFilter(obj, event); // Default processing // We have a QDynamicPropertyChangeEvent at hand QDynamicPropertyChangeEvent* pc = static_cast<QDynamicPropertyChangeEvent*>(event); // Not the correct dynamic property if (pc->propertyName() != "initialized") return QObject::eventFilter(obj, event); // Default processing // Value is false if (!obj->property(pc->propertyName()).value<bool>()) return true; QModelIndex idx = indexByName(obj->objectName()); setData(idx, true, SplashScreenListModel::InitializationRole); return true; }

OMG QFrame!

Hi and welcome to devnet,

Which version of Qt are you using ?

Hi,

You should run your application through a debugger. There's likely something else at play as emitting a signal without connection should not trigger any dangerous code path.

I also found Segoe UI as well as MS Shell Dlg 2 both of which are windows specific. What should I use to replace these?

@Pl45m4 Thanks for repsonding. I luckily found that repo yesterday and used the file but Visual Studio throws an error in the output and tells me that the "QCborContainerPrivate is undefined" yet in the watcher, it labels the unknown type as such. I'm currently back at square one it seems.

i have 6.9 beta 2, it is NOT fixed.
are you talking about 6.9 beta 3?

@Signal_Slayer: get_default_resource is from the C++ standard library. Check if you have deployed the MinGW runtime libs (like libstdc++-6.dll and libgcc_s_dw2-1.dll)

You should find them in c:\Qt\Tools\mingw1120_64\bin or whereever your MinGW is installed.

Regards

@Redman Thanks, but unfortunately, there is no portable version of this header file available...

@Simplicius-Simplicissimus said in Stylesheet for a subset of widgets:

I see that my attitude originates from a time when I participated in the production of generated code and drafted documentation for a Design Pattern course. Mission statements like “Aggregation is better than Inheritance” left their mark.

I know that currently there is a strong push against traditional OOP, especially inheritance. Inheritance is not a silver bullet and sometimes there are better solutions. But also, never using inheritance is also not a silver bullet. I'm not saying you should use inheritance instead of aggregation in general, but rather you should make an informed decision (instead of just blindly following rules like "Aggregation is better than Inheritance").

@Simplicius-Simplicissimus said in Stylesheet for a subset of widgets:

Qt has nothing to do with that.

Actually, Qt has something to do with that. Qt does not use interfaces/abstract classes. This is a design decision that was made and you have to conform to this with your own classes. Qt dictates that you MUST use inheritance instead of aggregation/composition. If you want to use Qt it is not your choice anymore (except for classes that don't directly interact with the Qt eco system).

As you have mentioned interfaces are implemented as abstract classes in C++. The mechanism is still inheritance to implement an interface. You gain nothing by using interfaces instead of just regular inheritance in C++. As I said before, you'd need to forward a lot of member functions when using aggregation. Nobody wants to write that much code! And with the design Qt has chosen you certainly don't need any dynamic_casts. Don't go through the trouble of rewriting Qt to use interfaces instead, just because of some stupid rule (most "rules" should actually be "guidelines"). BTW, the original design pattern book just collected patterns they observed in existing source code and gave them a name. The authors never said to force the patterns everywhere in your own code. If a pattern solves your problem–good, use it. But don't try to use as many patterns as possible. This was never the intention. Use them as guidelines.

@nicker-player said in how to change the position of the menu popped by the qpushbutton?:

it is not the operating system default style

What is your OS?
Did you do any styling already in your app?
There is documentation which should answer your question: https://doc.qt.io/qt-6/stylesheet-examples.html#customizing-qcombobox