Re: [Interest] Qt6 porting guidance: QMediaPlayer

this is really rather the crux of my software from what i can tell about Qt6, the removed functionality will make it impossible to have my software work? please tell me how i'm wrong? thanks > On Jul 7, 2021, at 6:59 PM, David M. Cotter wrote: > > in qt5 i could call mediaPlayerP->setVideoOu

Re: [Interest] Qt6 porting guidance: QCamera and QAbstractVideoSurface

does anyone who worked on Qt6 have any idea about this? to be clear: it chooses ONE of multiple cam inputs, and multiplexes the output to several QGraphicsVideoItems, each one in a different QGraphicsScene (not "the same scene in different viewers") > On Jul 7, 2021, at 12:58 PM, David M. Cotte

Re: [Interest] Qt6 porting guidance: (MSDEV) QMAKE_CXXFLAGS += /source-charset

> Please note that you can choose to use a different source character set, but > since Qt 5.0, the 8-bit strings passed to QString must be UTF-8. This is not > configurable any more, like it used to be. yes, i'm not constructing any QStrings using the file encoding. all my strings are handled in

Re: [Interest] Qt6 (win) linker help: LNK1104 cannot open file OleAut32

i don't even see the word "windows" there? and this isn't a library that I link to, it's just something that qt6 thinks my app needs to link to, so i have no say in its path... why did it want to link to a version i don't even have? and if it MUST link to it, how do i fix up the busted path? >

Re: [Interest] Qt6 (win) linker help: LNK1104 cannot open file OleAut32

On Friday, 9 July 2021 11:17:42 PDT David M. Cotter wrote: > the full error message is this: > > :-1: error: LNK1104: cannot open file > > :'Kits\10\Lib\10.0.19041.0\um\x64\OleAut32.Lib' > note i didn't even have that SDK version installed (19041), so why was it > looking in that SDK's folder? Loo

Re: [Interest] Qt6 porting guidance: (MSDEV) QMAKE_CXXFLAGS += /source-charset

On Friday, 9 July 2021 00:49:53 PDT Alexandru Croitor wrote: > I think adding > > CONFIG += no_utf8_source > > to your qmake project should help. Please note that you can choose to use a different source character set, but since Qt 5.0, the 8-bit strings passed to QString must be UTF-8. This is

Re: [Interest] Qt6: how to construct QVideoFrame from QImage ?

the correct implementation is this: (note it still does one extra copy, i do not know how to remove that) static QVideoFrame QVideoFrame_fromImage(const QImage& image) { QVideoFrameFormat frameFormat( image.size(), QVideoFrameFormat::pixel

[Interest] Text-To-Speech in QT6

Hi, I'm working on an app using Text-To-Speech, but QTextToSpeech isn't not present in QT6 apparently. There is plan to add this module to a future QT6 release? Or an alternative module exists? Thanks. -- Corentin (NVDA Expert 2019)

Re: [Interest] Qt6 porting guidance: (MSDEV) QMAKE_CXXFLAGS += /source-charset

Hi, I think adding CONFIG += no_utf8_source to your qmake project should help. > On 9. Jul 2021, at 03:26, Mike Chinander wrote: > > Does it let you remove the utf-8 option? > >> QMAKE_CXXFLAGS -= /utf-8 > > On Thu, Jul 8, 2021 at 8:20 PM David M. Cotter wrote: > all my source code was ori