Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Create code form OCX
Message
From
17/08/2007 22:19:00
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
 
To
17/08/2007 21:53:25
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01248795
Message ID:
01248908
Views:
26
Great question. If I knew more about this stuff I would probably have a great answer, but I'll muddle best I can.

I had a form that used the MSWinsck.ocx, had some of the properties/methods overwritten, and it worked great for what I needed it for. Unfortunately, I don't really understand all that it's doing, but I do want to use it because I already use it for another area (as a standalone service) of our application functionality. That one uses a form, though usually not visible, so I didn't have to be concerned too much the references to the visual OLE object. Now, I don't want the form, but still want the functionality. It wouldn't be a problem if it just referenced the OCX using its' default properties, but there have been changes.

This may be a poor question (yes, there are some), but if I want this as a non-visual class, and retain the code that someone added to the OLE object, do I need to rewrite all the methods and properties? Or can I simply reference directly what has not been changed, and "add" the methods properties in my PRG-based class to match what I see in the visual OLE object on the form?

If that didn't make sense to you, imagine how I feel...


>Hi Jay,
>
>creating the code from an OCX to that it can be converted to a PRG-based class is what you envision as a solution. What's the problem you are trying to solve?
>
>Hank
>
>>>>Is there a way to simply create the code from an OCX so that it can be converted to a PRG-based class?
>>>
>>>The question is unclear. You can always subclass it and when use Class Browser to get the code.
>>
>>My questions are always unclear it seems. Ok, if I can subclass it, is there an easy way to iterate through the procedure/methods and extract them to a PRG file? If your answer starts with anything along the lines of, "I'm not sure what you are trying to do..." then that tells me I will have to drop it and move on to something else because I'm not sure how to explain it in any more detail without throwing myself in front of the CLASSES train or from the OBJECT bridge. If that didn't make sense, then simply blame it on my quirky sense of humor and move on. "Nothing to see here folks..." <g>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform