HMGforum.com

CLEAR MEMORY!?

Wonderful Claudio.

Rathinagiri wrote:CLEAR MEMORY!?

Claudio,

IMHO This name of command is wrong because it will be dublicate of the existed Harbour command
My suggestion is

CLEAN MEMORY

Hope that useful

With the command RedrawWindow (BUSTA1.HANDLE) if the label also works if the whole is less fluid. Sorry but I do not understand why with HMG 3.4.0 (and I think also with HMG 3.4.1), this problem was not present while present with HMG 3.4.2 and also with patch_1
Thanks for the attention

Dear Claudio,
As commented Grigory, the MEMORY CLEAR command caused the application is closed, I changed it to CLEAN MEMORY as suggested and it worked properly.
Regarding the performance of the CLEAN MEMORY command works very well, I'm testing on a fairly large application memory and does not exceed 0.6 mb., The application is stable and no problems occur when applying the command.
About the solution, can you tell me how you determined who were the DynamicBackColor and DynamicForeColor blocks and nothing ?, because in the test that they never climbed used these properties.
I appreciate your dedication and generosity with us.
Best regards,
Luis Vasquez

Estimado Claudio,
Tal como comento Grigory, el comando CLEAR MEMORY provocaba que la aplicación se cerrara, lo cambié a CLEAN MEMORY como sugirió y funcionó correctamente.
Respecto al comportamiento del comando CLEAN MEMORY funciona muy bien, lo estoy probando en una aplicación bastante grande y la memoria no supera los 0,6 mb., la aplicación está estable y no se producen problemas al aplicar el comando.
Sobre la solución, me puedes decir como determinaste que eran los bloques DynamicBackColor and DynamicForeColor y no otra cosa?, ya que en los test que subi no se usaron nunca estas propiedades.
Agradezco tu dedicación y generosidad con nosotros.
Saludos cordiales,
Luis Vasquez

Dear,
I tell them that I am using the following settings:
Windows 10
HMG 3.4.2
It works very well with HMG has no problem or to compile or to run applications or printing documents. Get it all taped.
Thanks to all the team at HMG.
Best regards,

Estimados,
les comento que estoy usando la siguiente configuración:
WINDOWS 10
HMG 3.4.2
Se trabaja muy bien con Hmg, no tiene ningún problema ni para compilar ni para ejecutar las aplicaciones, ni la impresión de documentos. Todo funciona perfectamente.
Gracias a todo el equipo de HMG.
Saludos cordiales,

Hola amigo Rathinagiri

Con el nuevo parche del Dr. Claudio
hmg.3.4.2_patch_1.rar, sigue saliendo el
mismo problema al generar un informe en pdf
mediante HPDFPRINT, siguen las letras cayendo
viewtopic.php?f=43&t=4484&start=40
Un saludo
*------------------- Google -----------------*
Hello friend Rathinagiri

With the new patch of Dr. Claudio
hmg.3.4.2_patch_1.rar, is leaving the
same problem when generating a report in PDF
by HPDFPRINT continue falling letters
viewtopic.php?f=43&t=4484&start=40
A greeting
mustafa

gfilatov wrote:

Rathinagiri wrote:CLEAR MEMORY!?

Claudio,

IMHO This name of command is wrong because it will be dublicate of the existed Harbour command
My suggestion is

CLEAN MEMORY

Hope that useful

Thank Grigory for the tip.
I will change for RELEASE MEMORY.

srvet_claudio wrote:Hi Friends,
please test this patch:

Code: Select all

- Fixed bug in SetGridQueryData() in Win XP (reported by Eduardo Luis)
- Fixed bug in TrackPopupMenu() (reported by Esgici and Mustafa)
- Fixed bug in Transparent Label (reported by Emzampi)
- Fixed bug in Transparent property of BT_DrawText() function (reported by Andres Gonzales)
- Fixed bug in DynamicBackColor and DynamicForeColor of the Grid control when used with database (reported by Luis Vasquez)

- New internal function: HMG_Trace()

- New BT_DrawTextEx (hDC, Row, Col, Width, Height, cText, cFontName, nFontSize, aFontColor, aBackColor, nTypeText, nAlingText, nOrientation)

- New: now in Label control is possible to assign any data type or a list of data, e.g.
      - Form.Label.Value := xDataType
      - Form.Label.Value := { xDataType, xDataType, ... }
      
- New CLEAR MEMORY, release unused memory (leak memory), test for example:
      - ON KEY F5 ACTION ( CLEAR MEMORY )
      - DEFINE TIMER ... ACTION ( CLEAR MEMORY )

Hi Friends,
Please change the command name in file INCLUDE\i_window.ch line 823:
CLEAR MEMORY
for
RELEASE MEMORY

emzampi wrote:With the command RedrawWindow (BUSTA1.HANDLE) if the label also works if the whole is less fluid. Sorry but I do not understand why with HMG 3.4.0 (and I think also with HMG 3.4.1), this problem was not present while present with HMG 3.4.2 and also with patch_1
Thanks for the attention

Your application works well for me with hmg.3.4.2 patch 1.
You have rebuilt the library (c:\hmg.3.4.2\BuildLib.bat) ?

luisvasquezcl wrote:About the solution, can you tell me how you determined who were the DynamicBackColor and DynamicForeColor blocks and nothing ?, because in the test that they never climbed used these properties.

Sobre la solución, me puedes decir como determinaste que eran los bloques DynamicBackColor and DynamicForeColor y no otra cosa?, ya que en los test que subi no se usaron nunca estas propiedades.

The problem was that although the Dynamic Color is not specified, the grid established for default the Fore-BackColor as Dynamic Color.