2024-09-30, 13:04:46
Hello Richard,
Good detective work.
Yes, having the hard coded path there throwing that error makes perfect sense.
The question about if you can use IMPLEMENTS with a class name is more of a VFP question than an AntView one and I'm not a VFP expert. Having said that, the documentation suggests this should work for ActiveX controls and AntView is an ActiveX control, so yes I'd say that should work.
I tried the following in the new examples and the code still works.
So I guess that means yes.
Note that the latest release introduced a function to return the path of where the control is registered (RegisteredPath). But that info is likely to late for your code to be able to use it as you first need to instantiate the control to use it.
--
Wil
Good detective work.
Yes, having the hard coded path there throwing that error makes perfect sense.
The question about if you can use IMPLEMENTS with a class name is more of a VFP question than an AntView one and I'm not a VFP expert. Having said that, the documentation suggests this should work for ActiveX controls and AntView is an ActiveX control, so yes I'd say that should work.
I tried the following in the new examples and the code still works.
Code:
IMPLEMENTS IAntViewDocumentEvents IN "AntViewAx.AntViewDocument"So I guess that means yes.
Note that the latest release introduced a function to return the path of where the control is registered (RegisteredPath). But that info is likely to late for your code to be able to use it as you first need to instantiate the control to use it.
--
Wil