>>BTW- For what you are doing I don't think this is neccessary. You don't need an array of all the buttons on a form. Each button should handle the resizing itself via it's mousemove event. The form mousemove event should handle clearing any mods.
>>
>>hth
>>
>
>I'm not sure how the other buttons on the other forms would know how to resize themselves since they are no longer active.
They don't. Each object (including a form) knows what to do when a mouse is over it. So a buttons mouseover calls a thisform.sizefx.resizeme(this) method while a form's mousemove (or container) would call a thisform.sizefx.unsize() method.
The resizeme() method stores the object that was resized in a property. The unsize method just unsizes that object (if it's .null. nothing to unsize...)
Look at the _mouseoverfx class in the _FFC, it does almost the same thing (highlights instead of resizing). It's preeettty cool. I dropped it on a form and had CoolControls 2 minutes later. All Tim has to do is rewrite the code to resize instead of highlighting.
Actually it works with any object.
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!