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.

Messages - Dave Yeo

Pages: [1] 2 3 ... 322
Programming / Re: Qt6 Development
« on: May 19, 2024, 11:03:54 pm »
Finding a weird error trying to build my tree, same error I had before.
Building from dooble works as expected, run qmake ../ results in a message about QtCharts and a makefile. Whereas from dooble-dry, failure.
Code: [Select]
[L:\work\dooble\obj]qmake ../
Project MESSAGE: The QtCharts module has been discovered.

[L:\work\dooble\obj]cd ..\..\dooble-dry\obj

[L:\work\dooble-dry\obj]qmake ../
L:/QT6-6.2.X/mkspecs/features/toolchain.prf:76: Variable QMAKE_CXX.COMPILER_MACROS is not defined.
Project ERROR: failed to parse default search paths from compiler output

Weird. The files are identical, same environment.

Programming / Re: Qt6 Development
« on: May 19, 2024, 10:38:45 pm »
Thanks Dave! Working good here, also with new block list. One thing I notice with this one I didn't see before: at 'Settings'->'Web'-> 'Spell Checkers' there is a warning: 'en_US.bdic cannot be accessed!'. That file is available in the 'qtwebengine_dictionaries' directory and it worked with the 12/25/2023 version. Does it need to be updated or something?


Yes, something is not right. First this build is from the Dooble upstream repository rather then mine which I forked from the Bitwise repository. Maybe some missed patches? I'll update my repository and do more of a proper release later.
Here, I had to create the qtwebengine_dictionaries directory under obj/ where I built and launched the new build. While this changed the error, it changed it to something like "could not access /en_CA.bdic" and after copying en_CA.bdic to the root, the warnings went away.
I investigate after syncing repositories.

Programming / Re: Qt6 Development
« on: May 19, 2024, 08:29:21 pm »
Updated dooble_filter.txt and dooble_accepted_or_blocked_domains.txt from todays pull.

Programming / Re: Qt6 Development
« on: May 19, 2024, 08:17:07 pm »
Latest from Paul ran fine here, using Qt6Widge.dll it seems.
Here's a new build. I'll do a better one later.
Weirdly the build could not find most libs until I ran emxomf on them and then renamed them to remove the _dll. At least now the build works here.
Edit: this is todays pull
Edit2: fix so dooble_settings.db is stored correctly instead of in the root.
Code: [Select]
diff --git a/Source/ b/Source/
index c8a22672..7fce9c2f 100644
--- a/Source/
+++ b/Source/
@@ -278,7 +278,6 @@ int main(int argc, char *argv[])
   QString dooble_settings_path("");
-  dooble::s_application = new dooble_application(argc, argv);
 #if defined(Q_OS_WIN)
   auto bytes(qgetenv("DOOBLE_HOME").trimmed());
@@ -369,6 +368,12 @@ int main(int argc, char *argv[])
+  /*
+  ** Create the application after environment variables are prepared.
+  */
+  dooble::s_application = new dooble_application(argc, argv);
   ** Create a splash screen.

Weird that this is needed.

Utilities / Re: K File Wizard
« on: May 19, 2024, 12:55:24 am »

BTW, kfw.exe runs also if KCRYPTO.DLL is in /usr/lib directory  .

/usr/local/lib is usual for DLLs that aren't managed by the package manager.

Applications / Re: Archive tool problem
« on: May 06, 2024, 08:01:38 am »
The list of Available Warpin packages is empty - I have yet to see this ever populated.

Here, the list of available Warpin packages is pretty full. Likely I have the correct URL entered as given on the testers list some time back. Unluckily I can't share it and it has been long enough that I'm not even sure of that.

Applications / Re: Archive tool problem
« on: May 06, 2024, 03:32:15 am »
You could try moving x:\sys\apps\anpm\repo_1.wir out of the way with ANPM closed and retry.
Almost sounds like a bigger problem with your wordpro problem as well, hopefully not hardware.

Programming / Re: ClassiCube porting thread
« on: May 05, 2024, 05:26:24 pm »
There's %LIBC_THREAD_MIN_STACK_SIZE% to specify the minimum stack size for new threads. Default is 4096 bytes.
Seems there's a flag too but can't remember it.

Programming / Re: Any standard on exit codes?
« on: April 30, 2024, 01:26:36 am »
The "Control Programming Guide and Reference", installed by the toolkit as cp2.inf has a detailed list of error codes, about 64K different ones including reserved.
For GCC/Libc errors, see @unixroot/usr/include/sys/errno.h

General Discussion / Re: PMfax
« on: April 28, 2024, 04:05:28 am »
Ideally those basedev lines should precede the regular dev lines but the config.sys is parsed multiple times with the basedev lines parsed early, by  the mini-file system, so the result is a slightly slower boot.
I always had usbcom.sys towards the end of config.sys and it worked. Remming out the com.sys lines (and vcom.sys) for testing purposes seems the important step.

Programming / Re: SDL_mixer?
« on: April 27, 2024, 04:14:38 am »
It's easy to build, or use digi's build of SDL1,

General Discussion / Re: PMfax
« on: April 25, 2024, 10:36:04 pm »
You could try reming the com.sys lines in config.sys and removing the /m:3 from usbcom.sys for testing purposes.
I used to run a USR robotics USB modem, model #5637, worked fine until there was a thunderstorm. It was fragile and  storms killed 2 of them.

General Discussion / Re: PMfax
« on: April 25, 2024, 09:25:51 pm »
Try mode com1, mode com2 etc to see which com ports are installed. Seems I remember someone having problems as the com port was a higher then expected number.

Applications / Re: Nomacs Image Viewer
« on: April 24, 2024, 07:47:47 am »
Jasper-libs-2.0.22-1.c00 is in netlabs-rel but contains jasper.dll, not jasper1.dll

Programming / Re: Dive: Why does not this work
« on: April 22, 2024, 05:26:38 pm »
I wonder then, how SDL work then. There is not one mention of WM_VRN*. It just blits the whole SDL surface to the buffer (no direct VRAM access).

Cairo does the same. A comment in the code,
Code: [Select]
* This function uses DIVE to write those portions of the surface identified
* by @rect directly to the screen buffer.  It only supports 32- or 24-bit
* full-color video modes.  To avoid painting overlapping or child windows,
* it must perform all of the visible-region calculations that GPI normally
* handles.  Despite this, it provides a significant improvement in speed
* compared to using GPI functions.

Pages: [1] 2 3 ... 322