I still haven't resolved the logic (in my feeble mind) of "Every" component not having a Generic ComponentID assigned automatically at design time, in the accepted manner of the GUI Program languages that I am familiar.
"Unique" name assignment is up to the programmer at design time. This would lay the framework for future language enhancements that would allow access to the forms Collection of components. ----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Friday, June 03, 2005 9:01 AM Subject: [RBG7-L] - Re: Form Questions... >> (I haven't tested this code - but you get the id) > > Well, I get the _idea_! Getting the IDs is, of course, the problem. You're > right that it would be easier to do this at design time using the technique > you > described in 7.5, but it still has to be done (and maintained) at design time > by the programmer. > > If this information were available programmatically at runtime it would open > up > a whole new set of possibilities. You could write generic code that, when > called from the ON AFTER START eep could do all kinds of clever things to the > form it is called from. > > Javier's desire to turn all the components to read only is only example. You > could allow all kinds of generic form customizations. > -- > Larry >
