Unless it's already documented as clearly as you've done here Mark, this would make an excellent addition to the ooDialog reference, imho.
C.f. the flowchart describing the life-cycle of a Do-loop in the IBM Classic Rexx Reference. -Chip- On 1/13/2013 12:33 Mark Miesfeld said: > > Here is the internal flow in the framework when you invoke the execute > method: > > execute() > framework configures some basic stuff > framework gets the OS to create the underlying dialog > framework does some other work needed to get the dialog running > framework invokes initDialog() in your Rexx dialog > initDialog() executes and you do whatever > initDialog() ends ... > control returns to the framework > framework checks some other stuff > framework sets all the controls to values unless auto detection > is off > framework returns control to execute() > execute() regains control and runs until the underlying dialog is closed > > So, in your dialog where ever you invoked setText() it was *after* > control returned to execute(). > > Meaning it was after the framework sets all the controls to values. > > If you set the controls in initDialog(), or any other method invoked > from initDialog(), the framework will change the values of many of > those controls after you return from initDialog(). ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
