Build and Tested successfully in Windows 11

@moonyuet does this not have any of the Qt styling issues? e.g. the font issues or look issues on the Publisher UI and reports?

@moonyuet does this not have any of the Qt styling issues? e.g. the font issues or look issues on the Publisher UI and reports?

It still appears even when I tried to align PySide6 version in MD to 6.8.3 with the new build of the launcher.

But it still remained okay if we align both version to 6.7.1

Thanks @moonyuet - in that case I suppose tray publisher with this PR would also suffer from the issue.

I think we'll have to find a way to fix the styling with the newer Qt releases because it doesn't seem like that's being fixed in any of the newer releases (it's been there a while now.)

We'll need to ensure:

• The monospace font in the reports render correctly
• Background colors on the publisher UI in reports still look ok (are still covering full area)
• The publisher UI product types to choose from (on create tab) aren't suddenly higher in size.

Each of those issues are laid out here: ynput/ayon-blender#250 (comment) (including some screenshots)
Once we have solved all of those I think we have the liberty to update the Qt version.

The publisher UI product types to choose from (on create tab) aren't suddenly higher in size.

This is styling change in list view. For some reason list view in newer Qts does something weird, I had to set up margins to -5px to fix it (which is not right...).

Also not sure if it is in 6.8.3 too but in latest PySide6 custom delegate in combobox has the same issue (but that is easier to fix), which is used e.g. in projects combobox.

@moonyuet does this not have any of the Qt styling issues? e.g. the font issues or look issues on the Publisher UI and reports?

It still appears even when I tried to align PySide6 version in MD to 6.8.3 with the new build of the launcher. But it still remained okay if we align both version to 6.7.1

So seems like this font issue is fixable by setting an env var like:

"QT_QPA_PLATFORM":"windows:fontengine=gdi"

As reported here Qt6.8 changed the default font rendering engine on Windows to DirectWrite instead of gdi. The above workaround also came up in the comments of the Qt 6.8 release.

See also: https://doc.qt.io/qt-6/whatsnew68.html#platform-changes

Windows
Changed the font system to use DirectWrite as the default backend. This enables some modern features which were not available with the legacy GDI backend. The previous backend is still available and can be enabled by passing fontengine=gdi as parameter to the QPA plugin.

Possibly reverting to gdi maya then also drop the support again for font axes? So perhaps we should just start looking for a new font that doesn't suffer on Windows - because it seems limited to specific fonts only.

@moonyuet does this not have any of the Qt styling issues? e.g. the font issues or look issues on the Publisher UI and reports?

It still appears even when I tried to align PySide6 version in MD to 6.8.3 with the new build of the launcher. But it still remained okay if we align both version to 6.7.1

So seems like this font issue is fixable by setting an env var like:

"QT_QPA_PLATFORM":"windows:fontengine=gdi"

As reported here Qt6.8 changed font rendering and as came up in the comments of the Qt 6.8 release.

I would try to add the environment and see if it fixes the issue

@BigRoy The font issue has been fixed after adding the environment through application settings

You can also enable this upon the QApplication init via sys args... if that is more convenient.

class BlenderApplication:
    _instance = None
    blender_windows = {}

    @classmethod
    def get_app(cls):
        if cls._instance is None:
            # If any other addon or plug-in may have initialed a Qt application
            # before AYON then we should take the existing instance instead.
            application = QtWidgets.QApplication.instance()
            if application is None:
                if '-platform' not in sys.argv:
                    sys.argv += ['-platform', 'windows:fontengine=gdi']
                application = QtWidgets.QApplication(sys.argv)

            # Ensure it is configured to our needs
            cls._prepare_qapplication(application)
            cls._instance = application

does the same thing, enable the old font engine, would still be nice to find out why this looks so bad...

in regards to the Item Height in the create Dialog.

in the style.css #972

* Creator */
#CreatorsView::item {
    padding: 1px 5px;
    height: 1.2em;
}

adding the height helps to shrink them back down

So @iLLiCiTiT figured out the font issue. The new font engine seems to 'install' the fonts a different way making all the Noto Sans Mono static font variations we have register as the same "family" and hence, it'd install "Thin" variant last and end up using that. 🥲

The other families aren't being used currently - so we'll just remove those for the time being and all should be good. And we'll look to switching to single variable font (if that works well in the older PySide releases as well.)