Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Subclassing an OCX
Message
From
21/01/2000 14:13:27
 
 
To
21/01/2000 13:57:10
General information
Forum:
Visual FoxPro
Category:
ActiveX controls in VFP
Miscellaneous
Thread ID:
00319745
Message ID:
00321054
Views:
22
>Yeah, there is a very important difference between assigning an object to an existing property with CREATEOBJECT, and adding the Object Using o.AddObject or o.NewObject- the former does not add the object to the container, it merely gives the container a reference to the new object. Contained objects will be cleaned up when the container is destroyed, referenced objects will cause the container to hang because of an outstanding reference. And, as you found, there are certain controls that must live in the container, and not just be referenced by it.

Yep, there is a difference. While were on the ActiveX subject, how can you move a class that is an ActiveX from one classlib to another? If you open up 2 instances of the class browser and try dragging from one to the other, you get "object not valid for this container" error or words to that effect. The only way I've found to do this is to open the form designer, drop the class on it, and then do a save-as-class to the new classlib. Surely there must be a better/easier way?
Fred
Microsoft Visual FoxPro MVP

foxcentral.net
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform