I see some classes in FWH have a method by name Destroy(). If we name a method as Destroy, will it be called automatically, when the object goes out of reference ?
xharbour documentation mentions about DESTROYER method. Does it also called automatically?
Can any one clarify please?
Nageswararao,
>
I see some classes in FWH have a method by name Destroy(). If we name a method as Destroy, will it be called automatically, when the object goes out of reference ?
>
FWH automatically calls method Destroy() when a windows msg WM_DESTROY arrives:
http://msdn2.microsoft.com/en-us/library/ms632620.aspx
>
xharbour documentation mentions about DESTROYER method. Does it also called automatically?
>
FWH does not uses those methods, in order to have full control of what it is happening in the application
func main()
define window ownd MDI ....
.........
activate window ownd
release font ...
release brush ...
return 0nageswaragunupudi wrote:1) IF somewhere in one of the modules if we call WndMain():End(), does the control go to the statements after the main window's activate command and execute all release commands?
nageswaragunupudi wrote:2) If somewhere in one of the modules if we issue the statement QUIT, is there the danger that the resources are not destroyed/ released?
#include "Fivewin.ch"
FUNCTION MAIN()
LOCAL oWnd
DEFINE WINDOW oWnd
@ 1, 1 BUTTON "Test";
SIZE 100, 20;
ACTION oWnd:End() //MYQUIT()
ACTIVATE WINDOW oWnd
? "Exiting"
RETURN NIL
STATIC FUNCTION MYQUIT()
QUIT
RETURN NILnageswaragunupudi wrote:if so, is it good to keep the release statements in the EXIT PROCEDURE ?
Nageswararao, Enrico,
> Maybe the easier solution is to not use QUIT at all.
Right. QUIT should not be used at all.