Browse of my ADO Class

[Antonio Linares]

Dear Jose,

We have tested your hwgui example and we have found that dialogs can't be closed unless you close them in a specific (built?) order.
Unless you close the latest shown dialog, the others can't be closed.

You can download the built example from here:
https://github.com/FiveTechSoft/FWH_tools/blob/master/Dialogboxes.exe

source code:

Code: Select all  Expand view  RUN

#include "hwgui.ch"

static n := 1

FUNCTION Main()

   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadWaitForAll()
*
   RETURN Nil

FUNCTION Main2()

   LOCAL oDlg

   INIT DIALOG oDlg TITLE Str( n++ ) ;
     AT 200,0 SIZE 400,150

   ACTIVATE DIALOG oDlg

   RETURN Nil

continued in next post...

[Antonio Linares]

Using your example as a guide, we have detected and fixed where FWH was failing.

I am emailing you the modified FWH libs for bcc77. Please let me know if you need them for MSVC too.
Please confirm me that you get them, thanks.

Still it seems as we have something to fix when closing the dialogs. Sometimes they stop responding, still not sure why.
We can close them in any order, but sometimes they stop responding after closing a dialog. Searching for this...

We do appreciate your great feedback on this

[Antonio Linares]

Ok, we found it. It was the call to the garbage collector from Class TDialog Method End()

The solution is to call hb_gcAll( .F. )

Now it is working perfectly! You can close the dialogs in any order (something not possible with Alexander's lib)

Code: Select all  Expand view  RUN

#include "FiveWin.ch"

function Main()

   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadStart( { || Main2() } )
   hb_ThreadWaitForAll()

return nil

function Main2()

   local oDlg

   static nDlg := 1

   DEFINE DIALOG oDlg SIZE 400, 300 TITLE Str( nDlg++ )

   ACTIVATE DIALOG oDlg CENTERED

return nil

[Enrico Maria Giordano]

Antonio,

I'm trying to test your sample, but the program just end without any error or crash. What am I missing?

[Antonio Linares]

Dear Enrico,

You have to build it this way: (Harbour's multithread support)

samples\buildhmt.bat multi

[Enrico Maria Giordano]

Ok, hbvmmt.lib, thank you.

[JoséQuintas]

You can close the dialogs in any order (something not possible with Alexander's lib)

It is possible too, using an extra parameter when building library.

2021-10-31 04:50 UTC-0300 Jose Quintas
! source/winapi/hdialog.prg
! source/winapi/hwindow.prg
! Small change for multithread
Each thread will have it's own dialog and window list
activated only if compile using -DMT_EXPERIMENTAL
No change if do not compile using this parameter



Is this change on fivewin?

Code: Select all  Expand view  RUN

METHOD End( nResult ) CLASS TDialog
   ...
   SysRefresh()
   hb_gcAll(.F.)         // Garbage collector

   return .T.
 

Code: Select all  Expand view  RUN

test2.prg
dialog.prg
fivewin.hbc
-mt
 

No change for multithread.

[Antonio Linares]

Jose,

> It is possible too, using an extra parameter when building library

very good

> Is this change on fivewin?

Yes, included in the libs that I have sent you

[JoséQuintas]

Yes, included in the libs that I have sent you

Where I can found them ?

[Antonio Linares]

I sent them to your email

[JoséQuintas]

At momment no email.
I already check all folders including spam and deleted.

[Antonio Linares]

Please send me a whatsapp msg to +34 722461100

thanks!

[JoséQuintas]

working with multithread.
On menu

Code: Select all  Expand view  RUN

MENUITEM cDBF ACTION hb_ThreadStart( { || frm_funcMain( cDBF, aAllSetup,.T. ) } )
 

On dialogs: USE DBCLIENT ... CLOSE DATABASES
On all dialogs: click NEXT does a SKIP, and moves from 1 to 2
OK, this is multithread, each dialog have it's own dbf

WITHOUT multithread:
dialog 1: click next, does a skip, and moves from 1 to 2
dialog 2: click next, does a skip, and moves from 1 to 3
dialog 3: click next, does a skip, and moves from 1 to 4
dialog 4: click next, does a skip, and moves from 1 to 5
Ok, it is not multithread, all dialogs uses same dbf, and SKIP on same dbf.

No classes, no extra controls, basic USE/CLOSE.., and multithread.
Any dialog can call another routine, and current record will be the correct record.
No matter if change order, apply filter, or anything else on each thread.
Multithread is the same as several EXEs.
One thread/EXE does not change another.

Many thanks.

[Antonio Linares]

great work, excellent!