Mark, I think I've asked this before, but if so I can't find your response. So sincere apologies if you've already answered it.
The context is controls, and doing things to/with them. In the Guide, I'm trying to explain why some methods are on the control, while some are on the dialog with the control as a parameter. My current explanation in the Guide is as follows: "Note that in some cases the method invoked is directly on the control object, and in other cases the method belongs to the dialog object with the control being specified in a method parameter. The reason for this is that some methods (such as setText) are applicable to all controls, and so can be invoked on any control, while others (such as focusControl) have meaning within the context of the dialog as a whole." Now I know this is a simplification, but my question is, is the above text just plain wrong, or do you think it's close enough? Or do you think something should be added/changed? Many thanks, Oliver
<<attachment: winmail.dat>>
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Oorexx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-users
