[Interest] Is 6.x finally there ??

[Volker Hilsheimer]

Yo Roland,

> On 26 Oct 2022, at 20:52, Roland Hughes via Interest <interest at qt-project.org> wrote:
>>> On 20 Oct 2022, at 22:35, Scott Bloom <scott at towel42.com>
>>>  wrote:
>>> 
>>> I haven?t been following the 6.x progress very much.  Only because it was clear 6.0 and 6.1 were not ready to replace all the functionality of 5.x
>>>  
>>> However, with 6.4 it appears that all functionality that is going to be brought forward, has been completed.  Is that true? Or is there sill chunks of 5.x missing (that will be brought forward) ?
>>>  
>>> Scott
>>> 
> Hello Scott,
> 
> I feel compelled to point out only developers creating Qt responded with "Good to Go!". In particular the sticky wicket would be this quote
> 
> "and that we still want to bring back in some form"
> 
> Qt 6 has become the rental car company definition of "full sized" which now fits in the trunk of what most customers would call "full sized." They mentioned QtLocation and Bill Jones brought up
> 
> "Another missing module in Qt 6.x that is very important to desktop applications is clipboard support."
> 
> I don't know how anyone could create a desktop application without any form of clipboard support since users like to select from text file and paste answers into fields, especially if they are scraping answers out of an email or something like that.


What makes you think that Qt 6 has no clipboard support? You obviously didn’t bother with opening the referenced JIRA ticket.

What Bill pointed out as missing are the platform-specific classes that facilitate the integration of platform specific clipboard formats on Windows and macOS into Qt’s mime-based framework. Qt supports clipboard operations for common mime types just fine.


> You should probably also check here:
> 
> https://blog.basyskom.com/2021/porting-a-qt-5-application-to-qt-6/


Note that the basyskom blog is based on Qt 6.0. We are at Qt 6.4 now, and I would anyway almost think that you didn’t read it, given your implication that it must have been somehow difficult to port to this trunk-sized, clipboard-less Qt 6.


> Not that it matters to you, but not one of my clients is moving to Qt 6. Legacy products will continue to be maintained with Qt 4.8 custom spins as well as Qt 5.x custom spins but no new development will occur using Qt. That has been the feedback from one and all.


Indeed, what your clients do or don’t do would be a lot more interesting if we could assume that they get their information from someone who’s at least trying to keep up ;)


Cheers,
Volker