Recent Posts

Pages: 1 ... 8 9 [10]
91
Internet / Re: Dooble releases-Qt6
« Last post by Paul Smedley on November 30, 2024, 10:18:04 am »
92
Internet / Re: Dooble releases-Qt6
« Last post by Rich Walsh on November 30, 2024, 09:38:59 am »
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.

I'm sorry to see that this isn't the slam-dunk I hoped it would be. After the splash screen and before the main window is created should have worked. I've attached 'cppal030.zip' so you can confirm that changing the codepage manually works for you.

OK... just noticed something odd: using CpPal to drop the new CP on the main part of the window has no effect. I have to release MB2 while over the titlebar to get it to change. I looked at my notes for CpPal and discovered that it requires a bit more hack-ery to get this to work. CpPal has to fake a font-change in the window where you dropped to get it to notice and do an update.

Let's put this on hold for a bit while I figure out how and where to do this stuff. I'm quite certain that once we get the kinks worked out, just a few lines of code will give us a titlebar that isn't filled with question marks and wierdness :)

Meanwhile, Dave, can you give me a URL that points to your dooble_main.cc?
93
Internet / Re: Dooble releases-Qt6
« Last post by Paul Smedley on November 30, 2024, 06:57:24 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.
dooble_main.cc was my guess....
94
Internet / Re: Dooble releases-Qt6
« Last post by Dave Yeo on November 30, 2024, 06:18:50 am »
I also wonder if it should be in the webengine, which is basically chromium.
95
Internet / Re: Dooble releases-Qt6
« Last post by Dave Yeo 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.
96
Programming / Re: Bigicons
« Last post by David Graser on November 30, 2024, 06:01:03 am »
This is a two color folder - orange and yellow
97
Internet / Re: Dooble releases-Qt6
« Last post by Paul Smedley on November 30, 2024, 05:22:10 am »
Once we get this working, we should patch simplebrowser.exe too - I assume it has the same issue...
98
Internet / Re: Dooble releases-Qt6
« Last post by Rich Walsh on November 30, 2024, 05:12:13 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.)
99
Internet / Re: Dooble releases-Qt6
« Last post by Dave Yeo 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]
100
Internet / Re: Dooble releases-Qt6
« Last post by Dave Yeo 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?

Pages: 1 ... 8 9 [10]