Looking at the help it does say that the third parameter can be set to 1
at runtime, however it also says that any properties created at runtime
are public. I quote "The AddProperty( ) method makes it possible for
you to add a property to an object at run time. The new property is
added as a PUBLIC property." from the VFP9 help file. I apologize for
mistaking that you were trying to add a method to the object. I'm not
sure what I was thinking.
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com
Gene Wirchenko wrote:
> Jack Jackson <jacknospam@[EMAIL PROTECTED]
> wrote:
>
>> On Thu, 03 May 2007 10:12:43 -0700, Gene Wirchenko <genew@[EMAIL PROTECTED]
>
>> wrote:
>>
>>> The following line runs fine under a development system. Under
>>> the run-time, it throws error 1001 (Feature is not available.):
>>> browses.addproperty("filter1",chrtran(this.wfctlist," ",""),1)
>>>
>>> browses is an object of type basiccustom which is a subclass of
>>> custom. basiccustom simply adds a method called .dorelease() which is
>>> equivalent to most cl***** .release().
>>>
>>> this.wfctlist is an input field four characters long.
>>>
>>> browses.filter1 does not already exist (though this should not
>>> matter).
>>>
>>> The docs for .addproperty do not have anything about limitations
>>> under the run-time (except for the fourth optional parameter which I
>>> am not using).
>>>
>>> What am I missing here?
>> The do***entation lies, or it's a bug.
>>
>> When the third parameter is present you get that error when not in the
>> development environment.
>
> It is the fourth parameter that the do***entation says is not for
> the run-time. Why you can not set the exposure of the property during
> run-time is weird. I suspect an off-by-one error in VFP.
>
> Sincerely,
>
> Gene Wirchenko
>
> Computerese Irregular Verb Conjugation:
> I have preferences.
> You have biases.
> He/She has prejudices.
|
