Am 10.12.2012 19:32, schrieb oorexx-users-requ...@lists.sourceforge.net: > On Sun, Dec 9, 2012 at 10:06 AM,<amphitr...@ok.de> wrote: > >> >[...] > This is due to a "feature" of ooDialog called automatic data > detection. An attempt to explain it is made in sections 3.14.1, > 3.14.2, and 3.14.3 of the ooDialog documentation.
Yep, found it: "Obviously, the data attribute itself can not be accessed until it is created. For each type of class this is at a subtly different point in the life cycle of the dialog." > It is a feature from the original ooDialog implementation that I > personally don't care for. Mostly because it seems to be hard for > many people to understand. If you want to understand it, you will at > least need to read the documentation on it. Looks like a loop hole for the encapsulated variables of the child dialog object. Nice, but the last two paragraphs of sections 3.14.3 name it: it is what it is. > In the case of your program, one way to get it to work is to add this method: > > ::method initAutoDetection > self~noAutoDetection > > [...] Somewhat like 'user exits' where a program gives the user a chance to modify the processing. For such user exits Is there a similar list as 'Appendix C. Dialog Creation Methods' in 'ooDialog User Guide Version 4.2.0'? What leashes do we have to adjust that ooDialog? ;) > One of the many reasons I dislike data attributes / automatic data > detection is that it is very difficult to know or remember what the > data attribute name is going to be when it is created automatically. > It is explained as well as possible in section 3.14.2 Data Attribute > Names. For a programmer it would be nice to hold the reins of the processing. As such for debugging purpose at least I'd like a list of data attribute names. My little one-item Xmas wish list. :) > You do not*have* to have an init() method. Especially if you don't > do anything in the init() method as you show above. Thank you for validation of my supposition. > I'll have to review the User Guide, it shouldn't say that you > *must* have an init() method If not marked 'Optional' but 'Yes' it seems the paragraph before the table applies. [...] > The .InputBox is a stand alone dialog. The convenience dialog classes > like .InputBox, .SingleSelection, etc.. are only of use in the most > simplistic situations. You can not achieve what you want by using > them. So if I assemble an ooDialog window with many input fields it remains my problem to filter invalid input. Or is in the ooDialog framework somewhere a feature to reject unwanted values like excel can? [...] >> >BTW, is there somewhere a complement to the a. m. 'Appendix C. >> >Dialog Creation Methods' but for the "closing" methods like >> >leaving just for a quick and unambiguous overview - ah, no, maybe >> >I only have to re-read chapter 3.10. 'Standard Event Handling >> >Methods' 5 more times. > No about the appendix. And I believe you should only need to re-read > chapter 3.10*one* more time.;-) Yes, in theory I should, alas in practice No! <LOL> It's not your manual, it is due to my English. :) -------------------------------------------- Kostenlose E-Mail-Adresse mit unbegrenztem Speicherplatz für E-Mails, Free SMS und OK-Drive, der Online-Festplatte. Sicher Dir jetzt Deine Wunschadresse @ OK.de: www.ok.de ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
