Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
_SCREEN.ActiveForm=OLECONTROL not VFP Form
Message
General information
Forum:
Visual FoxPro
Category:
ActiveX controls in VFP
Miscellaneous
Thread ID:
00517109
Message ID:
00517585
Views:
24
>I do know that the OLEMISC status bits are stored in the registry like you say. However, looking at the code from the Delphi control creation you can see why that didn't fix the problem. The control itself has the status bits set during the creation of the control which is compiled into the OCX file.
>
>The registry entries are used by the container to read information about the control ahead of time before actually instantiating it. However, when the control does load it is setting the bits as compiled. It's too bad that it works that way. However, you can now tell MS how to fix the problem and just have them recompile it and send it back out! :-)
>
>However, I'm still debugging my control as far as when it instantiates within a Page of a Pageframe on a form. It does not appear when the form runs. Setting the Visible property to .F. and then to .T. has no effect. Even putting the control into a VCX wrapper has no effect. However, THISFORM.PageFrame.Page1.AddObject('MyOleControl') works OK!
>
>Very odd behavior again as well. So then I added code in the INIT of the form to add the object on the fly and then the control ends up showing up on the form and not in the page. However, when you click on the page the control then disappears from lying on top of the form and then reappears in the page properly. So much odd behavior!

Rich,

I had a feeling that the control you were speaking about was one that you created in Delphi. In all probability, my attempt to see if I could change the behavior of an ActiveX cotnrol was probably a "fool's errand". But, OTOH, I don't mind playing the fool if I learn something, and I did.

Whether or not VFP can be modified to deal with this sort of situation, I don't know. The fact that VB could, to me, isn't relevant. They're two extremely different environments. I think that the question that should be asked is, "Can the ActiveX controls provided by Microsoft be modified so that this isn't an issue?" I don't know the answer to this. Maybe Randy, or Calvin, or Mike do because I sure don't.
George

Ubi caritas et amor, deus ibi est
Previous
Reply
Map
View

Click here to load this message in the networking platform