On_Destroy's behavior has changed a bit.

Previously On_Destroy would only be called if the underlying connection was
still valid. This meant it was next to useless for Windows. However it
meant that in On_Destroy it was always safe to call methods on other Gnoga
objects.

This behavior has been changed and On_Destroy is called in all cases when a
Gnoga object is finalized. This means that if set on the window it can now
be used for clean up in singleton or multi_connect applications when the
connection has closed, something very useful. The connection should be
checked first in an On_Destroy if being set on a child element before
calling methods on other Gnoga objects.

Summary: On_Destroy is now a great place for clean up on loss of
connections when set on a Window.

David Botton
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Gnoga-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gnoga-list

Reply via email to