HMGforum.com

Pablo César wrote:

srvet_claudio wrote:
HMG_GETFREEMEM() --> GlobalMemoryStatusEx () [3]

Thank you Claudio for your explanation and indication. I just replaced and working perfectly, but only compile with HMG.3.3.0.

Is a new function of HMG.3.3.0

Pablo César wrote:Fijate Claudio que mi ToolBarButtons aparece y el fondo que era griz quede transparente para que el usuário pueda tomar los colores del desktop, pero quisiera que mi ToolBar apareciera. Y hé intentado de todo y habia desistido dejando apenas el desktop entero como pantalla capturada/exibida. Pero no me está capturando en el clipboard ni exibiendo en el StatusBar porque mi ToolBar no está más exibiendolo. Me gustaria hacerlo funcionar como quiero, cuando tengas un tiempito y me puedas mostrar el camino, te lo agradezco.

Ni bien pueda le doy una mirada a tu código.

OK, Claudio. Espero, gracias.

Hola Pablo César,

Solo curiosidad, que paso con este proyecto?

Saludos y un abrazo

Javier Tovar wrote:Hola Pablo César,

Solo curiosidad, que paso con este proyecto?

Saludos y un abrazo

+1

Thanks doc, very useful ( as always )

Regards

Javier Tovar wrote:Hola Pablo César,

Solo curiosidad, que paso con este proyecto?

Saludos y un abrazo

Desmotivación, Javier. Precisé ayuda y todavia no la obtuve.

Abrazos

Subscribe to this forum, and now I've found this topic which was very interesting, but I do not use FMG because I prefer PRG version where it is easier to inspect the code, so I'm used to

What confuses me with HMG are two syntaxes, standard xBase and alternative, sometimes not the same parameters, it's all there but a little different

I had a dilemma FMG or PRG so I decided to PRG

Now I have a dilemma standard or alternative syntax, is some better, maybe easier for the compiler or something?

Both have their advantages, but I wonder whether a better?

dragancesu wrote:I prefer PRG version where it is easier to inspect the code, so I'm used to

What confuses me with HMG are two syntaxes, standard xBase and alternative, sometimes not the same parameters, it's all there but a little different

In red color you mean FMG instead HMG, right ? Sorry I can not understand you when you said is standard xBase and alternative. What do you try to mean ? Give us examples to better understand you. You mean @ say... and DEFINE or what ?

That's what I meant

For each control in the HMG references are given two options and to

Standard Syntax (xBase Style):

@ <Nrow>, <NcoI>
BUTTON <ControlName>...
and

Alternate Syntax:

DEFINE BUTTON <buttonname>
PARENT <ParentWindowName>...

The second syntax is used to generate the files FMG

Whether something is better and why?

But this syntax question is just for retro-compatibilities. You can do it as you want, the important there are both way you can use and be defined in syntax.ch which is interpreted as must it be. This is not faster and nor lower way, it is just to simplify the way to use each elements.

For example, to make a BUTTON, HMG uses _DefineButton function and needs all following parameters:

<"name">,
<"parent">,
<col>,
<row>,
<caption>,
<{action}>,
<w>,
<h>,
<font>,
<size>,
<tooltip>,
<{gotfocus}>,
<{lostfocus}>,
<.flat.>,
<.notabstop.>,
<helpid>,
<.invisible.>,
<.bold.>,
<.italic.>,
<.underline.>,
<.strikeout.> ,
<.multiline.>

So, as It needs so many parameters, many of it can assume default value then i_altsyntax.ch helps to defining these missing parameters.

Regarding IDE is practically made to help in Forms creation and this forms is made strictly in the DEFINE way just because it is made by IDE program and it makes attending with all properties of each controls. But this FMG_Editor can uses both ways in FMG files, because HMG library permits to interpret as it needed for.

But your questins here is nothing with FMG_Editor, right ?