You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We last released with Qt6-only builds and almost nobody noticed. I think
we've had one Windows user and one Mac user notice. I DID change the
server-side upgrade message to not bug you if you were on an OS that
Microsoft had abandoned. I can't remember if I similarly added bumpers to
Mac users. Qt 6.3 officially "only" goes back to Mojave from 2018, but I
have 6.3.1 via Homebrew on my 2012 system that's still on Catalina.
Maybe QT6.2 LTS is a reasonable place to be. Even that's almost a year old,
so it's had some air time. We're nine months into its four year cycle.
I think our 32-bit and Windows 7 days are over. Niche users are always
welcome to build from source, struggling through whatever they need, and/or
keep running old builds that they already have.
On Fri, Jul 15, 2022 at 8:37 AM tsteven4 ***@***.***> wrote:
When the floor is Qt6 we can use QDateTime/QDate/QTime:fromString format
arguments to utf16 string literals.
—
Reply to this email directly, view it on GitHub
<#890>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3VAD25UE2OEPNFZFRLDELVUFSQ7ANCNFSM53VUBE2Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
When the floor is Qt6 we can use QDateTime/QDate/QTime:fromString format arguments to utf16 string literals.
The text was updated successfully, but these errors were encountered: