Paul,
The only way to clear something you've added to _Screen object is to do
explicitly or quit the VFP session. Because of your specific
application, you may want to add a note to the user. IMO, if you have
your startup program creating any kind of session variables, they should
be put on the _Screen object so you can be assured that they will endure
the entire session.
> -----Original Message-----
> From: profox-admin (AT) leafe .DO.T com [mailto:profox-admin@leafe.com]
> On Behalf Of Paul McNett
>
> Hmmm... so stuff attached to _SCREEN is never cleared?
> Never? If that's
> true, then yes I could attach to _SCREEN instead of declaring public
> variable references.
>
> The objects I'm instantiating are timers, and they have the
> smarts to commit
> suicide when their tasks are complete (good programmer?).
>
> Thanks Chad... assuming I'm relatively protected by attaching
> to _SCREEN,
> your idea should work. It still feels pretty draconian to
> issue CLEAR ALL
> all over the place, but it is another option. I don't like releasing
> something that when run could screw up somebody's setup.
©2003 J. Chad Bourque |
