OS/2, eCS & ArcaOS - Technical > Programming
Qt6 Application Testing
Dave Yeo:
You can also test with the window frame title with Qt5 using the DLL's at ftp://dry@ftp.os2voice.org/tmp/Qt5libs-2024-12.06.zip. Note that the window list patch that produces dots is not in these.
Roderick Klein:
--- Quote from: David McKenna on December 29, 2024, 04:13:13 pm --- Thanks Paul and Rich! I went to the Netlabs website where a bunch of QT6 apps are listed, but every one I tried would lock my computer solid, even without SET QT_PM_CP-1208. I'm guessing they were compiled with an older version of QT6, from before Paul changed the DLL names. So does anyone know of working QT6 apps compiled with the most recent QT6 (besides Dooble)? I'm happy to test...
Regards,
--- End quote ---
This is rather interesting. What programs have you got loaded ? Lock ups can also occur if all DLL's are not loaded high (marked for the kernel todo so). When testing you run other programs ?
Roderick Klein
David McKenna:
@Martin - actually I was using QT6 apps listed here: https://trac.netlabs.org/qtapps, but thanks for the link. I'll try some of Tellie's recent ones from there.
@Dave - if I put SET QT_PM_CP=1208 in CONFIG.SYS, it will effect both QT5 and QT6 (I have both recent hotfixes)?
@Roderick - I was testing with only what runs with the WPS, no other apps. If anything, I am guilty of loading too much into high memory, although I think I have that under control now...
Regards,
Dave Yeo:
Hi David, yes, the Window title patch that Rich came up with for Qt6 applied cleanly to Qt5 and works here with Dooble.
Roderick Klein:
--- Quote from: David McKenna on December 29, 2024, 10:29:45 pm ---@Martin - actually I was using QT6 apps listed here: https://trac.netlabs.org/qtapps, but thanks for the link. I'll try some of Tellie's recent ones from there.
@Dave - if I put SET QT_PM_CP=1208 in CONFIG.SYS, it will effect both QT5 and QT6 (I have both recent hotfixes)?
@Roderick - I was testing with only what runs with the WPS, no other apps. If anything, I am guilty of loading too much into high memory, although I think I have that under control now...
Regards,
--- End quote ---
When it comes to loading DLL's high there nothing to much you can load to high. However you should never mark OS2 DLL to high. Take for example PMMERGE.DLL or DOSCALL1.DLL.
Only mark data segments to load high. The key is to experiment with this to some extend. But only do this with large DLL's of QT for example.
The real weakspot of OS/2 os the lower shared kernel arena. If it runs out of memory, well, game over. Also loading large DLL's high will fragment the lower kernel memory area less.
Roderick Klein
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version