catonyx

Assertion failed in QM ve rsion 5.2.3, module classoperationsheet:269

Several of our projects have used it. It is hard to predict the future but we have no plan for using any time soon.

We use WSL1 and WSL2 as well as other VMs to compile while editing in Windows. To avoid the backslash vs slash issues, we put the license file in each folder(s) that has .qm files. <framework name="qpcpp" license="QPCPP-SP-XXXXXX.qlc"></framework> Maybe this can help.

We use WSL1 and WSL2 as well as other VMs to compile while editing in Windows. To avoid the backslash vs slash issues, we put the license file in each folder(s) that has .qm files. <framework name="qpcpp" license=".QPCPP-SP-XXXXXX.qlc"></framework> Maybe this can help.

QM 5.2.1 minor formatting issues

This is a very important feature for us too. We are bit behind on versions so we haven't noticed yet but we will eventually catch up and would have issue with this. Thanks for listening to feature requests.

I see how that would be difficult. It seems you might need to check in the generated code just for the review purposes know that you wouldn't edit it directly. We do merges on model qm files but only if there are no "drawing" changes. We have rendered qm files useless by bad merges. If someone is going to be pulling changes into a branch perhaps it should be the whole model not a merge. The reviewing should happen before a possible merge is needed or if there are drawing changes it should all or...

I would be okay with additional features but please don't change existing features. BTW, I always tell my co-workers to setup projects with relative directories whenever possible.