On Nov 29, 2006, at 1:08 PM, [EMAIL PROTECTED] wrote:
On Nov 29, 2006, at 19:57 UTC, Chuck Pelto wrote:
I guess that will work, but it strikes me as being a very code
intensive way of doing it.
How about another idea? One not so cumbersome?
It seems neither cumbersome nor particularly code-intensive to me.
Well....beauty, eyes, beholders.....you know....
I might introduce a local variable to replace the repeated
"c.Window.Control(i)" expression, but otherwise, it's just how I'd
do it.
I'm running into a problem with the line of code....
if c.Window.Control(i).Parent is me then
It's getting a property/method doesn't exist error during compile.
And Parent is not a propertly of Control Class.
If I have a name of the StaticText (ST) object that is a child of the
(thanks to your code example earlier this year)
ResizeableRelocatableRectangle (RRR), can I cast that into a ST
object I can work with?
No, but why not give ResizeableRelocatableRectangle a simple property
to keep track of this other control it needs all the time? You could
then either assign this property its correct value in the Open event,
or have the class find its own child using something like Charles's
code, the first time it needs it.
That's an interesting idea. If I could get Charles' code to compile.
Regards,
Chuck
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
