Dooble releases-Qt6

[Remy]

I have a question.

May it be possible the system frozen or hung state, silent dooble close etc... be a result of an audio driver issue ?  (uniaudio)
I know, that audio often stop working when playing an audio file and trying to watch a youtube video or when  switching youtube videos on the fly with a dooble hung followed by a system frozen state.

I did a high cpu utilization with ffmpeg using 3 different input stream and a very long complex filter with added time delays trying something special, during the run, audio drops working after several seconds... In many cases (like dooble), audio is the first stream not working !
 
Any idea ?

does dooble have the same issue when different video and audio drivers are used ? 

ps: Of course, I tried reducing mem size (having by default the highest possible value)

[Dave Yeo]

Interesting idea. Guess would need to compare to the USB audio driver. Another possibility is that part of MMOS2 is not SMP safe.

[Paul Smedley]

Looks like you haven't installed Paul's latest qos2.dll. You are right that they do display differently though, just not that different.

Right, here after replacing qos2.dll (better but not good)

Please roll back qos2.dll and test with https://smedley.id.au/tmp/qt6core-20241203.zip - this has a Proof of Concept fix from Rich.

Cheers,

Paul

[Remy]

Looks like you haven't installed Paul's latest qos2.dll. You are right that they do display differently though, just not that different.

Right, here after replacing qos2.dll (better but not good)

Please roll back qos2.dll and test with https://smedley.id.au/tmp/qt6core-20241203.zip - this has a Proof of Concept fix from Rich.

Cheers,

Paul

Yes, title bar is corrected but I saw something else...

The title into the xcenter bar isn't corrected.

[Dave Yeo]

Yes, the Window List also shows the old broken title. This is due to not using UTF8. I guess the Window list can't be fixed. Rich will have to comment on whether it is worth fixing the xcentre or whether fixing it would have side affects.

[Remy]

Yes, the Window List also shows the old broken title. This is due to not using UTF8. I guess the Window list can't be fixed. Rich will have to comment on whether it is worth fixing the xcentre or whether fixing it would have side affects.

QT5 doesn't have this issue...

Is something other missing ?
http://www.altsan.org/os2/toolkits/uls/ulsguide/index.html

[Dave Yeo]

Interesting. Guess there's another issue, probably codepage related. Try https://ru.ecomstation.ru/ and you will see the problem with Dooble-Qt5. See what Rich has to say as he is much more knowledgeable on this stuff then I am.

[Rich Walsh]

Yes, the Window List also shows the old broken title. This is due to not using UTF8. I guess the Window list can't be fixed. Rich will have to comment on whether it is worth fixing the xcentre or whether fixing it would have side affects.

If the final patches I sent you and Paul (in 2 emails) work as expected, this will all be resolved. Western European languages supported by CP850 should look correct everywhere. Russian/Chinese/etc. will display properly in the titlebar but have lots of question marks in the Window List.

[Remy]

I have a stupid question !

I found that QT uses a special font including latin etc.... for special characters.
Under \PSFONT I found WARPSANS.FON and WPSU.TTF as well WPSUB.TTF year 2017 (those before 2016 do not have latin.... chars
When I try to change font, the displaied font has by default a different font value then the one under Dooble QT5 (I expected to find the same string)
- Trying to change the font, I only found workplace sans and warpsans isn't into the list (workplace sans should be the same).
- Text rendering under QT5 build is not as defined, dark than under QT6 supposed to use the same font !  (is it using bitmap fonts or ot bitmap ?)
- Which fonts is QT6 using ? The right one including all special language with special chars ? - Does it have an included default font ? 

Regards

[Remy]

Yes, the Window List also shows the old broken title. This is due to not using UTF8. I guess the Window list can't be fixed. Rich will have to comment on whether it is worth fixing the xcentre or whether fixing it would have side affects.

If the final patches I sent you and Paul (in 2 emails) work as expected, this will all be resolved. Western European languages supported by CP850 should look correct everywhere. Russian/Chinese/etc. will display properly in the titlebar but have lots of question marks in the Window List.

Hi Rich,

I installed the qt6core and have default CP850 code page but as you can see, incorrect chars xcenter list ( the not displayed chars is é )

[Dave Yeo]

Hi Remy, you are going to have to wait for new builds. I'm currently rebuilding Qt5, Paul will have to rebuild parts of Qt6 and I will have to rebuild both Dooble's. Building Qt is slow.
As for fonts, I assume that only truetype fonts are supported by Qt. Dooble itself seems to reset the window title font on each new start. I haven't noticed any hard coded fonts and likely it is simply asking for a serif or such font and fontconfig takes care of choosing the actual font, though not really sure about it. There are also the fonts under settings.

[Paul Smedley]

Updated qos2.dll in https://smedley.id.au/TMP/qos2-20241204.zip - needs to be copied over \qt6-6.2.x\plugins\platform\qos2.dll

[Dave Yeo]

Updated qos2.dll in https://smedley.id.au/qos2-20241204.zip - needs to be copied over \qt6-6.2.x\plugins\platform\qos2.dll

Actually https://smedley.id.au/tmp/qos2-20241204.zip

[Rich Walsh]

Hi Remy, you are going to have to wait for new builds.

Actually, Remy, et al. are going to have to wait for even more new builds beyond those currently available.

Dave/Paul: in my window list patch, I used '.toLatin1()' to generate the switch list text. This is incorrect because Latin1 is not CP850 and produces the wrong accented characters. The screenshot shows QT5 on the left and QT6 on the right. Whatever QT5 does is the correct way to go (but _only_ for the switch list entry - the actual titlebar text must remain '.toLocal8Bit()').

[Paul Smedley]

https://doc.qt.io/qt-6/qtextcodec.html might help...

Code: [Select]

QTextCodec *codec = QTextCodec::codecForName("KOI8-R");
QByteArray encodedString = codec->fromUnicode(string);
IBM 850 is in the list of supported codecs.

scratch this, QTextCodec is part of qt5compat which can't be used in building qt6core