Harbour MiniGUI 2.6.7

[Roberto Lopez]

English:

- Fixed: Errors in documentation.

- Fixed: Problems with semi-oop preprocessor directives introduced
in 2.6.6. Reported by Marek and Grigory Filatov.

- Fixed: Problem with libhbmysql.a. Reported by Osvaldo Tambutti.

Español:

- Solucionado: Errores en la documentación.

- Solucionado: Problemas con las directivas de preprocesador (semi-oop)
introducidos en la versión 2.6.6. Reportado por Grigory Filatov.

- Solucionado: Problema con libhbmysql.a. Reportado por Osvaldo Tambutti.

[Rathinagiri]

Thanks a lot Roberto.

[esgici]

- Fixed: Problems with semi-oop preprocessor directives

Thanks and congratulations !

Although this update had been more painful, the result is perfect

Best Regards

--

esgici

[Roberto Lopez]

- Fixed: Problems with semi-oop preprocessor directives

Thanks and congratulations !

Although this update had been more painful, the result is perfect

Best Regards

--

esgici

Consistent handling of containers was in my head during years, but I've delayed because I knew that it could be a painful task

Regards,

Roberto.

[jas_sierra]

Greetings, Mr. Roberto when reifere to errors in documentation that is exactly mean, commands or functions that do not work properly with the parameters set?, Thanks for your time.

[rcain]

Roberto,

I am having a great time, relearning Clipper coding....
I am using the IDE to create screens, and have found that I need to write very little code!

I have come across one problem. or an difference in the way two controls work.
I am setting the FIELD property on TEXTBOX and DATEPICKER at design time.

The sequence of steps is as follows:

Function Process_Family_Members()

Load Window frmFamily_member

frmFamily_member.Center

DBGOTO(Recno)

frmFamily_member.Activate

Return Nil


When the screen is displayed, all fields contain data from the record, except
DATEPICKER, it contains the current date, no matter what is in the record.

If however, I execute the method:

frmFamily_member.txtDate1.Refresh && DATEPICKER Field
or if I load the value with:
frmFamily_member.txtDate1.Value := PEOPLE->Date1

after the DBGOTO command, the correct data will be displayed in the DATEPICKER
field on the screen.

The TEXTBOX controls work without the REFRESH method!

The work around is simple, but just something I have to remember to do…

Thanks for all of your work,

Robin D. Cain

[mol]

Hello Roberto!

Today (2.12.2008), I've installed my client my new application (compiled using hmg 2.6.7 and IDE 2.6.4)
On one screen user must fill some fields then press "SAVE" button for saving record into database.

Client has filled all fields, then using "tab" key set focus on "SAVE" button and (I don't know why....) pressed simultaneously ENTER on keyboard and left button on mouse.
And what happened?
Program saved two the same records into database - function under "SAVE" button has been executed two times!!! It's strange because there is "RELEASE WINDOW at the end of MySaveRecord function.

Tomorrow, I'll try to do it in my old application compiled with earlier version of hmg. I'll write about my observation...


P.S. Sorry for my poor English

Marek

[luisvasquezcl]

Roberto,
Como siempre, gracias por la nueva version.
Un abrazo,
Luis Vasquez

[mol]

I've compiled program using:
Harbour MiniGUI 2.0.031 (2007.06.26)
Harbour MiniGUI IDE 2.0 Build 2007.02.22

and have done test - press left mouse button on SAVE button and ENTER on keyboard - the same effect - two exactly the same records in database - function which save data was called two times and after that window was released.

How it is possible?

It is not big problem, but exists...

Marek

[gfilatov]

I've compiled program using:
Harbour MiniGUI 2.0.031 (2007.06.26)
Harbour MiniGUI IDE 2.0 Build 2007.02.22

and have done test - press left mouse button on SAVE button and ENTER on keyboard - the same effect - two exactly the same records in database - function which save data was called two times and after that window was released.

How it is possible?

It is not big problem, but exists...

Hello Marek,

Try the following workaround with a busy flag as below:

Code: Select all

/*
 * MiniGUI Hello World Demo
 * (c) 2002-2004 Roberto Lopez <harbourminigui@gmail.com>
*/

#include "minigui.ch"

Static lBusy := .F.

Procedure Main

	DEFINE WINDOW Form_1 ;
		AT 0,0 ;
		WIDTH 400 ;
		HEIGHT 200 ;
		TITLE 'Hello World!' ;
		MAIN ;
		ON INIT OpenTables() ;
		ON RELEASE CloseTables()

		DEFINE BUTTON Button_1
			ROW	10
			COL	10
			CAPTION 'Save'
			ACTION Save()
		END BUTTON

	END WINDOW

	CENTER WINDOW Form_1

	ACTIVATE WINDOW Form_1

Return

Procedure Save

if !lBusy
	lBusy := .T.
	append blank
	inkey(.2)
	lBusy := .F.
endif

ThisWindow.Release

Return

Procedure OpenTables()

	Use Test
	zap
	Go Top

Return

Procedure CloseTables()
	Use
Return

I hope that give you an idea.