HMGforum.com

Teaching someone else is not always an easy thing to do.

My problem is that if I create window 1 with a few buttons on it then all is ok.

I then create window 2 and add a few more buttons. No problem.

With both windows in view how do I stop the user from pressing buttons in the first window accepting that I want it to remain on display but in an inactive state.

I have written a little routine to disable the buttons in window 1 and it works ok but is there and existing command that does the same in a more professional way.

Hola amigo sunningdale:
Mirate en este sample que te puede
interesar mediante las PROCEDURE Anular()
Form_1.Buton_1.Enabled := .T.
Form_1.Buton_2.Enabled := .T.
y PROCEDURE Activar()
Form_1.Buton_1.Enabled := .F.
Form_1.Buton_2.Enabled := .F.
Anulas o Activas los Botones
Un Saludo
*---------------------------------------------*
Hello sunningdale friend:
Look in this sample you can
PROCEDURE interest using the Anular() <-- Cancel
Form_1.Buton_1.Enabled: = .T.
Form_1.Buton_2.Enabled: = .T.
and PROCEDURE Activar() <--On
Form_1.Buton_1.Enabled: = .F.
Form_1.Buton_2.Enabled: = .F.
Nullify or Active Buttons
a Greeting
Mustafa

sunningdale wrote:Teaching someone else is not always an easy thing to do.

My problem is that if I create window 1 with a few buttons on it then all is ok.

I then create window 2 and add a few more buttons. No problem.

With both windows in view how do I stop the user from pressing buttons in the first window accepting that I want it to remain on display but in an inactive state.

I have written a little routine to disable the buttons in window 1 and it works ok but is there and existing command that does the same in a more professional way.

Hi

Did you tried define MODAL type the second window ?

Happy HMG'ing

Many thanks to Mustafa and Esgici. You both helped a lot it now works perfectly.

sunningdale wrote:Many thanks to Mustafa and Esgici. You both helped a lot it now works perfectly.

You are welcome friend

Happy HMG'ing