>>>You can add specific code to the button
>>>

>>>... when button active the page
>>>this.parent.Addobj(this.name+"effect","shapeYellow",this)
>>>* shapeYellow bind it to the button ( move, anchor, .... )
>>>* deactivate
>>>this.parent.removeobject(this.name+"effect")
>>>

>>>
>>>unfortunately the VFP OOP model is not very flexible,
>>>and this code contaminates the Parent object because a button doesn't allow AddObject.
>>
>>Hi Fabio,
>>
>>After thinking a little bit more on the problem and speaking with my colleague (whos form this one is), I think we would put a shape on that container. Since button click's call common method, we would just operate this shape's coordinates and visibility.
>>
>>In other words, instead of a new class we would deal with the problem in the particular form's instance.
>
>hi Nadya,
>
>If I were you I'd rather add a property to the base class. The value of that property determines whether to show the yellow line

The problem is that we're not having custom button class. We have cCommandButton, which is a framework class. We don't have our acontrols. We have aCustomControls library with some specific custom controls.

Also it's almost impossible to make it a generic button control. Let me explain. When you click on the button, you want to give it this effect. However, when you click on a different button, you want to remove the effect. The problem is: how would you know in the button class what you clicked on another button? <g>

That's why it would be much easier to handle in the parent class (container in our case).