<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><category>pcsoft.us.windev</category><copyright>Copyright 2026, PC SOFT</copyright><lastBuildDate>12 Jun 2017 17:11:39 Z</lastBuildDate><pubDate>11 Jun 2017 11:02:16 Z</pubDate><description>From WinDEV Manual: "The object is created during its declaration. The object is local by default."&#13;
&#13;
I have two Windows, Win1 and Win2 and declared Class MyClass&#13;
&#13;
//Win1&#13;
//Global declaration Win1&#13;
gclTest is MyClass&#13;
&#13;
//after processing click BTN_New to open Win2&#13;
Open(Win2)&#13;
&#13;
&#13;
//Win2&#13;
//Global declaration Win2&#13;
gclTest is MyClass&#13;
&#13;
//after processing return to Win1&#13;
RETURN&#13;
&#13;
&#13;
After returning to first window the class gclTest is destroyed.&#13;
If I use different name, everything is OK.&#13;
&#13;
So, how it is possible if object is local by default, as manual say?&#13;
&#13;
Any clue?</description><ttl>30</ttl><generator>WEBDEV</generator><language>en_US</language><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan/read.awp</link><title>Object naming and lifespan?</title><managingEditor>moderateur@pcsoft.fr (El moderador)</managingEditor><webMaster>webmaster@pcsoft.fr (El webmaster)</webMaster><item><author>fromweb</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61268/read.awp</comments><pubDate>12 Jun 2017 17:11:39 Z</pubDate><description>Hi,&#13;
&#13;
You are right, and I have been using that technique for years, with the &#13;
same object name declared in separate windows (…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61268/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61268/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan/read.awp">Object naming and lifespan?</source><title>Re: Object naming and lifespan?</title></item><item><author>BigED</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61267/read.awp</comments><pubDate>12 Jun 2017 16:51:22 Z</pubDate><description>Hm..&#13;
&#13;
It's GLOBAL just for the WINDOW, like any other variable. Isn't it?&#13;
&#13;
If declared as LOCAL than this object is unaccesi…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61267/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61267/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan/read.awp">Object naming and lifespan?</source><title>Re: Object naming and lifespan?</title></item><item><author>fromweb</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61262/read.awp</comments><pubDate>12 Jun 2017 14:50:46 Z</pubDate><description>Hi Ed,&#13;
&#13;
it is local by default.&#13;
If you declare it in the GLOBAL declarations of the windows, then of &#13;
course it is GLOBAL (a…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61262/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan-61262/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/61241-object-naming-and-lifespan/read.awp">Object naming and lifespan?</source><title>Re: Object naming and lifespan?</title></item></channel></rss>
