Messages

1

Internet / Re: Dooble releases-Qt6

« on: December 04, 2024, 04:48:24 am »

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

2

Internet / Re: Dooble releases-Qt6

« on: December 04, 2024, 03:18:59 am »

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.

3

Internet / Re: Dooble releases-Qt6

« on: December 03, 2024, 11:36:40 pm »

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.

4

Internet / Re: Dooble releases-Qt6

« on: December 03, 2024, 05:11:08 pm »

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.

5

Internet / Re: Dooble releases-Qt6

« on: December 03, 2024, 05:13:46 am »

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

6

Internet / Re: Dooble releases-Qt6

« on: December 02, 2024, 06:19:23 pm »

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

7

Internet / Re: Dooble releases-Qt6

« on: December 02, 2024, 05:30:52 am »

That was why I enabled it, hoping there was a software GL stuff in there somewhere.
It did produce some interesting trps.

8

Internet / Re: Dooble releases-Qt6

« on: December 01, 2024, 11:35:39 pm »

I'm using the default userstring, today not only am I getting the cloudflare thing, but it is crashing the browser, simply vanishing at first, then when I tried a new profile, crashed recursively, 10 trp files, all sigaborts. Finally tried the Qt5 build and still got stuck in the loop of it checking and failing.
It was on the SeaMonkey newsgroup, alt.comp.software.seamonkey now as Mozilla shut down its newsgroups, that people were blaming the lack of WebGL support for the cloudflare problems.

9

Internet / Re: Dooble releases-Qt6

« on: December 01, 2024, 06:04:29 pm »

I noticed this in dooble_main.cc,

Code: [Select]

#ifdef Q_OS_WINDOWS
  QCoreApplication::setAttribute(Qt::AA_UseSoftwareOpenGL, true);
#endif
Tried adding Q_OS_OS2 to the ifdef, webgl crashed the browser when used. So read up on it, https://doc.qt.io/qt-6/windows-graphics.html.
It is to load a non standard 3D driver including a software solution, they suggest Mesa llvmpipe which would need lvm. There are other software OpenGL drivers around such as TinyGL or PortableGL. Mentore has built TinyGL and I've built PortableGL previously IIRC.
The problem to overcome is that Cloudflare has become the gatekeeper of much of the internet with it's "Are you human" checks. These depend on WebGL to display, so we just get a spinning circle. Even a really slow 3D renderer would be better then nothing for these cases. And actually, given a small window, software OpenGL often doesn't perform too bad.

10

Internet / Re: Dooble releases-Qt6

« on: December 01, 2024, 05:28:24 pm »

The Qt5 build is currently the same as the Qt6 build when it comes to the titlebar, lots of question marks. It just didn't have the problems with the other weird characters that you fixed.

11

Internet / Re: Dooble releases-Qt6

« on: November 30, 2024, 05:41:00 pm »

Meanwhile, Dave, can you give me a URL that points to your dooble_main.cc?

https://github.com/dryeo/dooble/blob/master/Source/dooble_main.cc

12

Internet / Re: Dooble releases-Qt6

« on: November 30, 2024, 06:18:50 am »

I also wonder if it should be in the webengine, which is basically chromium.

13

Internet / Re: Dooble releases-Qt6

« on: November 30, 2024, 06:16:07 am »

How to set this up?

OK, if HMQ_CURRENT resolves to the number '1', try plugging in a '1' for now, i.e.:  WinSetCp(1, 1208);

(I should know how to do a new-style cast but that bit of knowledge escapes me currently.)

Well, I've tried adding the code in various places that seemed early enough in the process, mostly in dooble_main.cc and even right after QApplication::processEvents(); in dooble.cc and no luck.
Guess going to have to read up on how Qt initializes unless Paul has an idea.

14

Internet / Re: Dooble releases-Qt6

« on: November 30, 2024, 04:48:04 am »

I get,

Code: [Select]

[H:\tmp]test
"\xE2\x82\xAC"
Ôé¼
"?"
"\xE2\x82\xAC"
Ôé¼


Redirecting stderr to a file then loading it in qe with utf8  encoding gives,

Code: [Select]

"\xE2\x82\xAC"
€
"?"
"\xE2\x82\xAC"
€
[/quote]

15

Internet / Re: Dooble releases-Qt6

« on: November 30, 2024, 04:44:32 am »

I have NFI about this stuff.

Given all this, I would strongly, strongly recommend implementing this fix in Dooble itself and *not* in QT6 since other QT6-based apps may handle their titlebars differently. To do so, add the following code to Dooble early in its processing: probably right after it initializes the QT6 framework and no later than after it creates its first window (the primary thread's message queue has to exist for this to have any effect). This should only be used on the very first thread.

Code: [Select]

WinSetCp(HMQ_CURRENT, 1208);


OK, tried putting this just before the splash screen, earlier used

Code: [Select]

#ifdef Q_OS_OS2
#define INCL_WINCOUNTRY
#include <os2.h>
HMQ hmq;
#endif
Dies with,

Code: [Select]

K:/work/dooble-dry/Source/dooble_main.cc: In function 'int main(int, char**)':
K:/work/dooble-dry/Source/dooble_main.cc:432:12: error: 'HMQ_CURRENT' was not declared in this scope; did you mean 'FILE_CURRENT'?
  432 |   WinSetCp(HMQ_CURRENT, 1208);
Found this in pmwin.h,

Code: [Select]

#define HMQ_CURRENT          ((HMQ)1)
which dies with,

Code: [Select]

K:/work/dooble-dry/Source/dooble_main.cc:55:36: error: use of old-style cast to
'HMQ' {aka 'long unsigned int'} [-Werror=old-style-cast]
   55 | #define HMQ_CURRENT          ((HMQ)1)
      |                                    ^
K:/work/dooble-dry/Source/dooble_main.cc:432:12: note: in expansion of macro 'HM
Q_CURRENT'
  432 |   WinSetCp(HMQ_CURRENT, 1208);
      |            ^~~~~~~~~~~
cc1plus.exe: all warnings being treated as errors

How to set this up?