Brainstorm

@Sarreq-Teryx as an aside.

KDE is still on Qt5 and are slowly moving over to Qt6 today. The various features your mockup requires are only available in the latest Qt6, so you're probably asking a bit early. Like asking about pretty wallpaper while the foundation is just drying.

Just to close this topic out, here's what I ended up doing (posted elsewhere as well):

// will need one of these for each subclass void EquipmentModel::sendPatchRequest(const Vsp &equipment) { sendBaseRequest(equipment); } void EquipmentModel::sendBaseRequest(const Equipment &equipment) { ... // the line below will call the override function // for the appropriate subclass. equipment.addPatchFields(listEntry, qjo, rolesToKeys);

Not super elegant, but it works. Thanks to all for the suggestions.

Just to close this out, I'm pursuing the subclass approach to this. Thanks for the suggestions.

So I simply needed handle one more signal:

QObject::connect(reply, &QNetworkReply::errorOccurred, &loop, &QEventLoop::quit);

@jsulm

Hi,

I have update the project - ".pro" file and it working and building the project and I am adding the dependence for all the connect project files.

Thanks

Fixed it -- I added a bool to my parent property to tell me whether this button belongs to to the start or end panel, and I check that bool in my callback.

Button { id: action buttonText: actionButtonLabel onClicked: { stackView.clear() stackView.push( actionComponent, { "listModel": scheduleActionPanel.actionModel, "listIndex": isStartPanel ? newSchedule.startAction : newSchedule.endAction, "buttonGroup": startStopGroup, "titleText": scheduleActionPanel.actionTitle, "callback": ((i) => { if (isStartPanel) { newSchedule.startAction = i } else { newSchedule.endAction = i } } ) } ) } }

If necessary, the bool could be replaced by an int, and the callback logic made more elaborate.

Hi @Bradyok, and welcome!

Yes, it's a bug in Qt Creator 11.0.2: https://bugreports.qt.io/browse/QTCREATORBUG-29506 It will be fixed in v11.0.3.

In the meantime, you can install and use v11.0.1: https://download.qt.io/official_releases/qtcreator/11.0/11.0.1/ or use @S_M_R's workaround

@SimonSchroeder Thanks so much for the suggestions everyone, I truly value the input from others that are most definitely more talented than myself.

@Podugu You should also check Linux logs (dmesg for example). It really looks like your desktop session is terminated for some reason (I guess something is crashing).
What graphics hardware and driver do you use?

@TomZ said in controls that don't really "control":

My personal advice on the usecase where getting a new state may take more than 200ms is to have your datamodel update the state after 250ms to "waiting-for-state-B" or something (use a timer) and then the front-end can show the 3rd state, indicating that its busy doing what you requested.

I agree completely -- it's just a little hard to figure out how to do this with a Switch.

EDIT:

I got my issue with the Switch figured out - it wasn't so much a state problem as it was my lousy model implementation (explained in painful detail elsewhere in the forum). Thanks to all for the help.

It probably could be built using Qt WebAssembly,
as it looks to be javascript based.

@myneur The us.kmap from that link is valid. However, it does also generate around 40 warnings as the other two do.

Do you still need the qmap files ?

@Hannibal said in Some advice for a table application:

What about the first and last columns, should I merge the cell for have the same look as pics?

https://forum.qt.io/topic/123343/qtableview-qtablewidget-cell-span-range

Search the web and this forum, there's numerus topics on this.

@SGaist maybe it's because I'm old school, or maybe it's because I have enough trouble reading other people's code, but...whatever the reason, I prefer to explicitly derive a function's return value, assign it to a variable, and return that variable. I realize it accomplishes nothing, and in the absence of a good optimizing compiler, is actually fractionally slower, but...it's just how I roll.

@TomZ I ended up taking Jeremy's suggestion, and it works beautifully. Keeps the message manager self contained and no need for state awareness.