General information
Category:
Coding, syntax & commands
>>>>My .02 worth.
>>>
>>>...and worth it;) But in this particular case had the code included This.parent I'd still be facing the same issue, since the parent would be the page frame itself.
>>
>>Exactly! So what do you do but make concessions or create command button classes specifically for your pageframes?
>
>You've hit on the heart of why I called it a philosophical issue. In this case, do I create command button classes specifically for this (anticipating I might again need this) or make concessions? I'm not really expecting an answer as in "Go forth and make classes", because I suppose you can overclass, or would that be declasse(where's that accent grave when I need it:) But seriously, I know that some people sub-class extensively perhaps for this very reason.
In another language that I use, I like the idea of unique names of controls. It doesn't matter what control is contained within what. A container is _not_ necessarily the parent. Like Jim said, maybe this is addressed in Tahoe. I know that some typing could be eased as well. I know I love typing ThisFormSet.Form1.MyPageframe.Page6.MyOtherPageframe.Page2.MyContainer.MycommandButton.MyMethod :)
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only