Qt 6.5 Beta Released With New Modules

[carewolf]

Restoring my app's window position upon restart is frowned upon? By whom? Some "way smarter than thee committee?" It's my computer and my app -- it should do what I want, not some "stupid shit" forced on me by the "way smarter than thee committee."



I *am* the user. These are apps I write for myself to use.

By the designers of Wayland. They want an ideal world where apps know nothing about where they are, and have no impact on it. It is on of the flaws of the initial idea, we are slowly getting workarounds for the millions issues that decision caused.

[ed31337]

App-configured window position was frowned upon even on Xorg and it was described as "optional", even if most toolkits and WMs allowed it. Window position is meant to be managed by the WM alone.

Restoring my app's window position upon restart is frowned upon? By whom? Some "way smarter than thee committee?" It's my computer and my app -- it should do what I want, not some "stupid shit" forced on me by the "way smarter than thee committee."

By the way, how do you dare to say that it is *irritating to you* that you cannot control window position based on your whims? You're trying to force some stupid shit down the throats of your users, LOL! Let your users call it irritating instead.

I *am* the user. These are apps I write for myself to use.

[curfew]

Is it possible to set the window position in my code using Qt 6.x on Wayland yet? That is one of the most irritating missing features for me in Qt 5.15 with Wayland. Some (non-Qt) programs manage to do it, so don't try to tell me this can't be done on Wayland.

Wayland sets absolutely no restrictions on what can be done. Anything is possible but you might have to roll your own private protocol extension for the features (and write the code implementing them) if there is no standard protocol defined yet. But obviously no-one else will support that private feature then and it's pointless to whine if no-one else therefore has that feature.

App-configured window position was frowned upon even on Xorg and it was described as "optional", even if most toolkits and WMs allowed it. Window position is meant to be managed by the WM alone.

By the way, how do you dare to say that it is *irritating to you* that you cannot control window position based on your whims? You're trying to force some stupid shit down the throats of your users, LOL! Let your users call it irritating instead.

[ed31337]

Is it possible to set the window position in my code using Qt 6.x on Wayland yet? That is one of the most irritating missing features for me in Qt 5.15 with Wayland. Some (non-Qt) programs manage to do it, so don't try to tell me this can't be done on Wayland.

Also would be really nice if the memory leaks in Qt WebEngine were solved.

[curfew]

I was more pointing at the fractional scaling support. That's the blurriness KDE users complain about right? Great that it's fixed.

Wayland didn't even have (standard) fractional scaling until one month ago. Your point makes absolutely no sense at all then.

[rafanelli]

You are not getting it right, Qt has not been lagging in their Wayland-game as you claim.

I was more pointing at the fractional scaling support. That's the blurriness KDE users complain about right? Great that it's fixed.

[Morty]

Now we are on 6.5 and still the experimental tape is on.

You are not getting it right, Qt has not been lagging in their Wayland-game as you claim. Qt support for Wayland has been excellent for years. A curios fact about that, you could buy commercial products using Qt on Wayland quite a while before any of the Linux desktops was able to even run an experimental Wayland session.

What is new in 6.5 is a Wayland Native Interface, and that is very advanced use-cases functionality not needed in most applications. Besides this was already possible in Qt5, but in a less clean manner. Now a better way has been introduced in QT6.

[skeevy420]

Wow, thanks!

Maybe it's the fact that you used Google instead of Duckduckgo that I'm using by default.
And the non-descriptive or cryptically names didn't help either.

I honestly expected to see the changelog on this page:
https://www.qt.io/blog/commercial-lt....15.7-released
And I guess I was not the only one, seeing the comment on that page.

No problem. I did a shot in the dark search with commit message of Merge Qt 5.15.7 opensource release and the mailing list with the changelog link was the first Google result which, luckily enough, is exactly what I was hoping to find. The same search on DDG didn't find that page with the release notes link. It did find some very close links like projects in the same repo as qtreleasenotes, but that's still two or three degrees of separation...

[rafanelli]

Qt made a big mistake by lagging in their Wayland-game. You want to be a cross-platform toolkit? Well, Wayland is the new platform on Linux that eventually every serious app will support. You, Qt, could have seen this coming.

Now we are on 6.5 and still the experimental tape is on.

Glad it's improving though. I like the APIs they offer much better than GTKs.

But there is a Wayland-first alternative being build, "iced", and for Linux only apps it may soon overtake Qt as my fav.

[Danny3]

My dumbass found it in under three minutes using a less-than-known service called Google Search. It's in an obscure repository named "qtreleasenotes", under some non-descriptive directories like "qt/5.15.7", and in a file cryptically named "release-note.md".

Wow, thanks!

Maybe it's the fact that you used Google instead of Duckduckgo that I'm using by default.
And the non-descriptive or cryptically names didn't help either.

I honestly expected to see the changelog on this page:

https://www.qt.io/blog/commercial-lts-qt-5.15.7-released

And I guess I was not the only one, seeing the comment on that page.