HMGforum.com

I attach the .EXE file because DynamicFont property of GRID/TREE Controls will be implemented in the next release.

yessssssssssssssssssss
I badly need it !!!

thank you compa !

bpd2000 wrote:

esgici wrote:Exploring innovations in 3.3.1 -- 2

( The first (Global Memory Status Extended Sample) is here )

Process information by new process functions.

ProcInfo.PNG

ProcInfo.zip

Thanks to Dr. Soto

Thank you Esgici

Is process ID and Handle are same ?
If not how to get Handle from Process ID
We can get/add windows title name property, Handle in Grid example

esgici wrote:

srvet_claudio wrote: ...
Another example.
...

Thanks Dr., good enhancement

By adding TerminateProcess(), the sample has been a good Task Manager

By the way, the SET WINDOW MAIN OFF/ON is what I'm looking for; separate thanks to this

Regards

I have not tested but you can do by
SendMessage( FindWindow( 0, "Title of Window" ), WM_CLOSE ) to terminate window

bpd2000 wrote:

bpd2000 wrote: Is process ID and Handle are same ?

Creo que el ID y el Handler es lo mismo, solo que el ID es todo el proceso y el handler es una encapsulacíon que te permite obtener solo las funciones disponibles de ese proceso.
seria caotico que tengas acceso a todo el proceso y destruir toda la PILA del programa accediendo a el en forma directa.

es como una Clase que solo tienes acceso a sus Metodos.

manejador, identificador, descriptor, Muchas veces el origen de usar distintos nombres es debido al framework (con sus sutiles diferencias) de donde proceden, tampoco hay que comerse la cabeza con discrepancias semánticas.

Translate Google
I think the ID and Handler is the same, only the ID is the whole process and the handler is an encapsulation that allows you to get only the functions that process available.
would be chaotic to have access to the entire process and destroy all STACK accessing the program directly.

it's like a class you have access to only their Methods.

handler, handle, descriptor, often the origin of using different names is due to the framework (with subtle differences) from which, we must not eat the head with semantic discrepancies.

Exploring innovations in 3.3.1 -- 3 : Get / Set Cursor Positions functions
Thanks Dr. Soto

esgici wrote:Exploring innovations in 3.3.1 -- 3 : Get / Set Cursor Positions functions

Thanks Dr. Soto

Thank you Esgici

esgici wrote:Exploring innovations in 3.3.1 -- 3 : Get / Set Cursor Positions functions

Hi Esgici,

I have a small correction for usage of the function SetCursorPos().

It should be
SetCursorPos( nCurCol, nCurRow )

instead of
SetCursorPos( nCurRow, nCurCol )

in your sample

gfilatov wrote:

esgici wrote:Exploring innovations in 3.3.1 -- 3 : Get / Set Cursor Positions functions

Hi Esgici,

I have a small correction for usage of the function SetCursorPos().

It should be
SetCursorPos( nCurCol, nCurRow )

instead of
SetCursorPos( nCurRow, nCurCol )

in your sample

Thanks to your interest Dave and Grigory

Thanks to correction, Grigory

Regards

Hola Sr. Esgici,

Buen ejemplo!, gracias por compartir.

Saludos

Exploring innovations in HMG -- 4 : SET WINDOW ... commands

Another new feature ( announced before HMG 3.3.1 ) is SET WINDOW ... commands

A small sample is here ( In addition to C:\hmg.3.3.1\SAMPLES\Miscellaneous\ScreenSplash sample of official release ).

Thanks Dr. Soto