True, that's easier if all you want to do is disable helptags. But I'm
assuming that the idea is to give the user an option, which they may choose
to exercise while the window is already open, in which case you'd also need
some way to restore the helptags. Which is why I suggested a subclass/class
interface approach, because that would simplify turning them back on.
George
On 6/1/02 13:53, Adam Ernst wrote:
> Well, you could create a class interface, but it would be easier (and in
> my opinion, simpler) to put this in the open event of all your windows:
>
> dim i as integer
>
> if shouldDisableHelpTags = true then
> for i = 0 to controlCount-1
> control(i).helpTag = ""
> next
> end if
>
> Adam
>
> On Saturday, June 1, 2002, at 11:37 AM, Buddy wrote:
>
>> George et al...
>>
>> The only place I can find documentation about class interfaces is in the
>> docs when they speak of control bindings.
>>
>> Is there some more thorough description of what a Class Interface is?
>> What
>> ones exist now for controls? How one can make their own?
>>
>> Thanks,
>> Paul K
>>
>>> Subclassing the controls (with our without a Class Interface to tie
>>> them
>>> together; the Class Interface would simplify it a bit) should make this
>>> pretty easy to do.
>>
>>
>> ---
>> Subscribe to the digest:
>> <mailto:realbasic-nug-digest at lists dot realsoftware dot com>
>> Unsubscribe:
>> <mailto:realbasic-nug-off at lists dot realsoftware dot com>
>>
>
>
> ---
> Subscribe to the digest:
> <mailto:realbasic-nug-digest at lists dot realsoftware dot com>
> Unsubscribe:
> <mailto:realbasic-nug-off at lists dot realsoftware dot com>
|