1
Internet / Re: Dooble releases-Qt6
« on: Today at 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.
OS2 World Community Forum
OS/2, ArcaOS and eComStation - Warp Community
News:
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Internet / Re: Dooble releases-Qt6
« on: Today at 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.
It did produce some interesting trps.
3
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.
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.
4
Internet / Re: Dooble releases-Qt6
« on: December 01, 2024, 06:04:29 pm »
I noticed this in dooble_main.cc,
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.
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.
5
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.
6
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
7
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.
8
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.
9
Internet / Re: Dooble releases-Qt6
« on: November 30, 2024, 04:48:04 am »10
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?
11
Internet / Re: Dooble releases-Qt6
« on: November 30, 2024, 03:27:20 am »
I get,
Remember that the command shell has no knowledge of unicode. At that, I'm not aware of any cmd line utility that does have knowledge of UTF.
BTW, your updated qt6code.dll didn't seem to help here, just changing the glyphs in a wrong way.
Code: [Select]
[H:\tmp]test
"\xE2\x82\xAC"
Ôé¼
"?"
"\xE2\x82\xAC"
Ôé¼
Remember that the command shell has no knowledge of unicode. At that, I'm not aware of any cmd line utility that does have knowledge of UTF.
BTW, your updated qt6code.dll didn't seem to help here, just changing the glyphs in a wrong way.
12
Internet / Re: Dooble releases-Qt6
« on: November 28, 2024, 07:12:12 pm »
Hi Remy, I see what you mean. Seems to be a problem with up-streams choice on how to implement translations. I'll play some more with changes to the translate URL, might have to raise an issue upstream.
I note that SeaMonkey gets it right.
I note that SeaMonkey gets it right.
13
Internet / Re: Dooble releases-Qt6
« on: November 27, 2024, 12:22:03 am »
OK, created a basic test page with ÀŽƒ in the title. SeaMonkey and Dooble-Qt5 fail to display Ž with SM showing an underline and Dooble-Qt5 showing a question mark for the missing glyph. Dooble-Qt6 shows garbage. The title bar does seem capable of displaying UTF8 as long as the font has the glyph but something goes wrong with Dooble-Qt6, almost seems like it is translating it to cp850 here.
Save as something like test.html and try loading the file.
Looking at the screen shot, you see the glyphs do display in the tab.
Code: [Select]
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Test Page. ÀŽƒ </title>
</head>
<body>
<br>
</body>
</html>
Save as something like test.html and try loading the file.
Looking at the screen shot, you see the glyphs do display in the tab.
14
Internet / Re: Dooble releases-Qt6
« on: November 26, 2024, 10:58:37 pm »
The problem seems to be the dash, which is not ascii. See how it displays here,
–
Normal dash,
-
SeaMonkey does display it fine in the text but not in the title bar, where it is an underline. Could it also be a font problem? Or simply the WPS has problems with non-ascii characters in the titlebar? Dooble-Qt5 also fails to correctly display the en dash or whatever it is though it displays a question mark.
Edit: It's U+2013 : EN DASH according to Babelstone.
–
Normal dash,
-
SeaMonkey does display it fine in the text but not in the title bar, where it is an underline. Could it also be a font problem? Or simply the WPS has problems with non-ascii characters in the titlebar? Dooble-Qt5 also fails to correctly display the en dash or whatever it is though it displays a question mark.
Edit: It's U+2013 : EN DASH according to Babelstone.