How to Guify your 32-bit Harbour Text App

Based on my limited experience, you may convert your 32-bits Harbour text to gui via

a) gtWVT
cch4clipper.blogspot.com/2011/02/simple-usage-of-gtwvt.html

b) gtWVW - Sudip is the expert on this ;-)

c) gtWVG - you can incrementally add GUI to your old Clipper codes
cch4clipper.blogspot.com/2009/04/using-harbourwvg-part-i.html (there are 4 parts to this series)

d) HMG stable .3.0.35 (compatible with Harbour 2.0 only) - Need rewrite
cch4clipper.blogspot.com/2009/03/adding-gui-to-xharbourharbour-via-hmg.html
cch4clipper.blogspot.com/2009/05/reporting-with-hmg-part-i.html (2 parts series)
cch4clipper.blogspot.com/2009/03/mapping-clipper-command-to-hmg-commands.html

e) HMG Extended aka Minigui (Needs rewrite)
cch4clipper.blogspot.com/2009/03/mdi-programming-with-minigui.html
cch4clipper.blogspot.com/2009/03/programming-mdi-with-minigui-pat-ii.html

I have successfully used hbmk2 for

a) gtwvg

cch4clipper.blogspot.com/2011/02/building-harbourgtwvg-project-using.html

b) hmg
cch4clipper.blogspot.com/2011/02/how-to-compile-hmg-application-hbmk2.html

c) Minigui
cch4clipper.blogspot.com/2011/02/how-to-build-minigui-hmg-extended.html

Cheers

CCH

Harbour/xharbour Diff : 9/57 - FUNCTIONS WITH VARIABLE NUMBER OF PARAMETERS by Przemyslaw Czerpak

### FUNCTIONS WITH VARIABLE NUMBER OF PARAMETERS ###
==========================================================
Both compilers supports them though xHarbour is limited to all parameters
and does not support unnamed parameters. In Harbour you can declare some
named parameters and then unnamed just like in many other languages, f.e.:
func f( p1, p2, p3, ... )
The unnamed parameters can be used in different statements passing them
by '...' operator, f.e. as array items:
proc main()
AEval( F( "1", "2", "A", "B", "C" ), {|x, i| qout( i, x ) } )
func f( p1, p2, ... )
? "P1:", p1
? "P2:", p2
? "other parameters:", ...
return { "X", ... , "Y", ... "Z" }
or as array indexes:
proc main()
local a := { { 1, 2 }, { 3, 4 }, 5 }
? aget( a, 1, 2 ), aget( a, 2, 1 ), aget( a, 3 )
func aget( aVal, ... )
return aVal[ ... ]

or as function parameters:
proc main()
info( "test1" )
info( "test2", 10, date(), .t. )
proc info( msg, ... )
qout( "[" + msg +"]: ", ... )

The '...' operator saves references when push parameters and it can be
used also in codeblocks, f.e.:
bCode := { | a, b, c, ... | qout( a, b, c ), qout( "[", ..., "]" ) }

All parameters can be accessed also using hb_aParams() function but
in xHarbour it works correctly only for functions which does not use
any local parameters or declared with variable number of parameters
or when number of declared parameters is not smaller then number of
passed parameters. This code illustrates it:
proc main()
p1("A","B","C")
p2("A","B","C")
p3("A","B","C")
p4("A","B","C")
p5("A","B","C")
proc p1
? procname()+"(), parameters:", pcount()
aeval( hb_aParams(), {|x,i| qout(i,"=>",x) } )
proc p2
local l
? procname()+"(), parameters:", pcount()
aeval( hb_aParams(), {|x,i| qout(i,"=>",x) } )
proc p3(x)
? procname()+"(), parameters:", pcount()
aeval( hb_aParams(), {|x,i| qout(i,"=>",x) } )
proc p4(...)
? procname()+"(), parameters:", pcount()
aeval( hb_aParams(), {|x,i| qout(i,"=>",x) } )
proc p5(a,b,c,d,e)
? procname()+"(), parameters:", pcount()
aeval( hb_aParams(), {|x,i| qout(i,"=>",x) } )

In xHarbour it's only possible to declare all parameters as unnamed, f.e.:
func f( ... )
and then access them using hb_aParams() or PVALUE() (in Harbour it's called
HB_PVALUE()) function. There is no support for named parameters and ...
operator.

In xHarbour due to reverted behavior of references stored in array items
assign operation to items in array returned by hb_aParams() changes
corresponding parameters passed by reference. It does not happen in
Harbour where item references stored in arrays work like in Clipper.

Harbour MiniGUI 1.9 Extended Edition (Build 95) Released

CCH : From the HMG Extended Forum

Hi All,

The Harbour MiniGUI 1.9 Extended Edition (Build 95) setup is published at the following URL:

http://hmgextended.com/files/CONTRIB/hmg-1.9-95-setup.zip

There is the following changelog for this build:

2011/04/12: Build 95 (HMG 1.9 Extended Edition) Published.
* Fixed: Problem with assigning the plain text to the RichEdit control
(introduced in the build 94).
Bug was reported by Paolo Russignan <paolorus@yahoo.it>.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Fixed: Cleaning of warning at BCC 5.8.2 in the source\c_richeditbox.c
(introduced in the build 94).
Problem was reported by Rossine <qiinfo@ig.com.br>.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Fixed: Timer was fired at the 'Value' property changing in the disabled state.
It exists in the official version too.
Problem was reported by Jaroslav Janik <jaroslav.janik@siemens.com>.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Enhanced: Panel window supports now the conjoint form of spelling for events
and properties (OnInit, OnRelease, VirtualWidth, VirtualHeight,
FontName, FontSize) at definition similar to others kind of windows.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Enhanced: 'Address' property of Hyperlink control can contain the procedure name:
- ADDRESS "proc:\\MyProc()" for execute the user function.
Based upon a contribution by Sasha Savov ;
(see demo in folder \samples\Basic\HYPERLINK)
* Changed: Fixed warnings at the compilation in MinGW32 (tested for 3.18).
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Updated: HBPrinter library v.2.24 (see source in folder \source\HbPrinter):
- Fixed: C-code cleaning for warnings with MinGW32.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Updated: MiniPrint library (see source in folder \Source\MiniPrint):
- Fixed: C-code cleaning for warnings with MinGW32.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Updated: Adaptation FiveWin Class TSBrowse 9.0 in HMG:
- Fixed: Missing ADS tag order support in the SetDbf method.
Contributed by Igor Nazarov.
- Fixed: Code cleaning for warnings with MinGW32.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
* Updated: Harbour Compiler 2.1.0rc2 (SVN 2011-04-10 12:43).
Contributed by Grigory Filatov <gfilatov@inbox.ru>
(look at ReadMe.txt in folder \harbour)
* Updated: HMGS-IDE v.1.0.7.1. Project Manager and Two-Way Visual Form Designer.
Contributed by Walter Formigoni <walter.formigoni@uol.com.br>
(look for what's new at changelog.txt in folder \Ide)
* New: 'Tone function via sound card' sample.
Based on code contributed by Andi Jahja <harbour@cbn.net.id>.
Contributed by Grigory Filatov <gfilatov@inbox.ru>
(see in folder \samples\Advanced\Tone)
* Updated: 'TBrowse SpecHeader' sample for compatibility with TSBrowse 9.0 syntax.
Contributed by Janusz Pora <januszpora@onet.eu>
(see in folder \samples\Advanced\Tsb_
SpecHeader)
* Updated: 'Multi Richedit' sample.
Contributed by Janusz Pora <januszpora@onet.eu>
(see in folder \samples\Advanced\RicheditEx_2)

This release of MiniGUI is considered stable and ready for production use.

Your comments/feedback are welcome!

--
Best Regards,
Grigory Filatov
[MiniGUI Team]

The Harbour HowTo Tutorial Rev. [51] IS BORN !

CCH : From the Harbour Developers Group


Hi
The Harbour HowTo Tutorial Rev. [51] WAS BORN !
It is available at:
http://www.gruppoeratostene.com/harbour/harbour-tutorials.htm
Regards
Giovanni Di Maria

P.S.
This tutorial in now very small, but in future it will become
important.

Harbour/xharbour Diff : 8/57 - DETACHED LOCALS AND REFERENCES by Przemyslaw Czerpak

When local variables are used in codeblocks then it's possible that
the codeblocks will exist after leaving the function when they were
created. It's potentially very serious problem which have to be resolved
to avoid internal VM structure corruption. In Clipper, Harbour and
xHarbour special mechanism is used in such situation. Local variables
are "detached" from VM stack so they are still accessible after leaving
the function, f.e.:
      proc make_cb()
         local n := 123
         return {|| ++n  }
We call such variables "detached locals".
Here there are two important differences between Clipper and [x]Harbour.
In Clipper variables are detached when function exits (returns) and it
does not know which variables were used but simply detach whole local
variable frame from VM stack. It's very important to know that because
it can be source of serious memory problems in OS like DOS.
This simple code illustrates it:

      // link using RTLINK and run with //e:0 //swapk:0
      // repeat test second time with additional non empty parameter 
      #define N_LOOPS 15
      #xcommand FREE MEMORY => ? 'free memory: ' + ;
                                 AllTrim( Str( Memory( 104 ) ) )
      proc main( x )
         local n, a
         a := array( N_LOOPS )
         FREE MEMORY
         for n := 1 to N_LOOPS
            a[n] := f( x )
            FREE MEMORY
         next
      return
      func f(x)
         local cb, tmp, ref
         tmp := space( 60000 )
         if empty( x )
            cb := {|| .t. }
         else
            cb := {|| ref }
         endif
      return cb

If you execute above program with non empty parameter then 'tmp' variable
is detached with codeblock which uses 'ref' variable and not released as
long as codeblock is still accessible. It means that in few iterations
all memory are allocated and program crashes. Clipper's programmers should
know that and be careful when use detached local and if necessary clear
explicitly other local variables before returning from the function by
setting NIL to them.
In Harbour and xHarbour only variables explicitly used in codeblocks
are detached and detaching is done when codeblock is created and original
local variables are replaced by references. It is possible because Harbour
and xHarbour support multilevel references chains so it works correctly
also for local parameters passed be reference from parent functions.
In Clipper only one level references are supported what creates second
important differences. When Clipper detaches frame with local parameters
then it has to unreference all existing references breaking them. This code
illustrates it:

      proc main()
         local cb, n := 100
         mk_block( @cb, @n )
         ? "after detaching:"
         ? eval( cb ), n
      return
      proc mk_block( cb, n )
         n := 100
         cb := {|| ++n }
         ? "before detaching:"
         ? eval( cb ), n
      return

Above code compiled by Clipper shows:

      before detaching:
             101        101
      after detaching:
             102        101

so after detaching the references to 'n' variable is broken and codeblocks
access his own copy of this variables.
In Harbour it works correctly so the results are correct and it shows:

      before detaching:
             101        101
      after detaching:
             102        102

In xHarbour ( for unknown to me reasons ) Clipper bug is explicitly emulated
though it was possible to fix it because xHarbour inherited from Harbour
the same early detaching mechanism with multilevel references so just like
in Clipper xHarbour programmers have to carefully watch for possibly broken
references by detached locals and add workarounds for it if necessary.

Harbour/xharbour Diff : 7/57 - PASSING OBJECT VARIABLES BY REFERENCEby Przemyslaw Czerpak

Both compilers support passing object variables by reference though this functionality in xHarbour 

is limited to pure instance or class variables only and does not work for SETGET methods. 

In Harbour it works correctly.

This code illustrates the problem:

      proc main()
         local oBrw := tbrowseNew()
         ? oBrw:autoLite
         oBrw:autoLite := !oBrw:autoLite
         ?? "=>", oBrw:autoLite
         p( @oBrw:autoLite )
         ?? "=>", oBrw:autoLite

      proc p( x )
         x := !x

Harbour prints:
      .T.=> .F.=> .T.
but xHarbour prints:
      .T.=> .F.=> .F.
without generating any compile or run time errors.

HMG.3.0.36 is now Compatible with HB 2.1rc2

CCH : Thanx to Rathi from the HMG Forum, HMG 3.0.36 can now be compiled with Harbour 2.1 rc2 Code: - HMG 3.0.36 (Test) 2011/03/19 Changelog:    - Built using latest Harbour Nightly Build (2011/03/16)    - Following Modifications done on official HMG 3.0.35      * Edit in \hmg\source\c_media.c - Replace line no. 144 with the following:      //    hwnd=MCIWndCreate((HWND) hb_parnl(1),NULL,Style,hb_parc(2));      * Edit in \hmg\source\h_init.prg - Replace line no. 628 with the following:          _HMG_SYSDATA [ 306 ] := ( EMPTY( CreateMutex( , .T., strtran(GetProgramFileName(),'\','_') ) ) .OR. (HMGGetLastError() > 0) )      * Edit in \hmg\source\c_winapimisc.c - Replace line no. 416 to 419 with the following:       HB_FUNC ( HMGGETLASTERROR )       {         hb_retnl( (LONG) GetLastError() ) ;       }      * Edit in \hmg\source\h_windows.prg. Replace line no 5588 with the following:             uResult := CallDll32 ( "IsAppThemed" , "UXTHEME.DLL"  )    - Changed HMG Build system to hbmk2 by adapting HMG 4 and latest Harbour method.    - Changed HMG Build Application System by adapting HMG 4. Please make use of newbuild.bat in samples folder or buildapp.bat in hmg main folder.