Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
June letter on Visual FoxPro web site
Message
 
To
02/06/2005 04:16:38
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01019035
Message ID:
01019264
Views:
19
He, he,

But I need This:
_Screen.AddObject("tool","_tool")
?_screen.tool.Run()
CLEAR ALL
?_screen.tool.Run() && where is my tool?

define CLASS _tool AS custom
  name="_tool"

  PROCEDURE Run()
    wait wind "tool..."
  ENDPROC
enddefine
MartinJ

>NOPE.
>
>Try this:
>
>_SCREEN.AddProperty("Myprop","Hello!")
>CLEAR ALL
>?_SCREEN.Myprop
>
>Still there!
>
>
>
>>Hi John,
>>
>>Isn't good example, because CLER ALL release all object references and classes.
>>
>>MartinJ
>>
>>>Hi Colin!
>>>
>>>_SCREEN?
>>>_VFP?
>>>
>>>These are what we use in testing to avoid the CLEAR ALL issue.
>>>
>>>>
>>>>The VFP team has looked at the CLEAR ALL issue carefully back to the VFP 3.0 days, and there has never been a good solution to implement based on the fact that those tools are VFP objects in the same memory space.
>>>>
>>>>Just give us one new system variable - _TOOLCOLLECTION - that can take an object reference, that doesn't get cleared with CLEAR ALL. We'll do the rest.
>>>>
>>>>- Colin
"Navision is evil that needs to be erazed... to the ground"

Jabber: gorila@dione.zcu.cz
Jabber? Jabbim
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform