Hello Mark! To your append from last month: [...] >> >My question: is there something like a >> >'super-expose' to join the variable pools of two or more objects? >> > > > No, there isn't. At least not anything I'm aware of.
It is written in ooRexx Reference Version 4.1.2, p. 4: 'The data is said to be encapsulated because the only way to access it is through one of these surrounding actions.' That is OO, it is what it is. >> > >> >Why I ask: I use ooDialog to show a Window what is represented as >> >an object in ooREXX. From a menu I start a "child" dialog which is >> >also an object. Alas a new object with its own variable pool. > > > I think the word should not be "alas" but "Thank goodness." Thank goodness > the new object has its own variable pool. I am not convinced. Transparency is strength. (Is this why mangers like power.slides?) At least it is a paradigm shift: in REXX I know and like, you had to 'protect' _actively_ a subroutine's variables by using the keyword 'procedure', otherwise the variables of a subroutine did use the variable pool of the calling routine. No headache how to transfer data structures set up in variables to and from a method/subroutine. Well, I assume, you will not change that just for me. :) To be fair I must concede that an object-bound variable pool has it's advantage when you need the same object more than once. So my difficulty is only that a sub-dialog or child dialog is a new object, 'isolated' from the parent dialog. Or did I overlook something and there is an alternate way to pop up a dialog window by selecting a system menu item? > The one thing you can use, which you might not be aware of being used to > procedural programming, is the "attribute" directive. > [...] > you will have some, limited, access to the exposed variables posX and posY > through the "attribute" method. Thank you. works. I just bracket the execute() with two assignments like this: subdlg~fxFlag = fxFlag subdlg~execute() fxFlag = subdlg~fxFlag what looks a bit confusing as I used the same varialbe name in the parent and child dialog. This hand over of a value I must repeat for ervery variable I need in the child dialog. And repeat again for every child dialog. What leads me to the question if something like .constDir[..] could be used to build a 'super variable pool'. > I'm not too good at explaining things, I think you need to actually use > "attributes" some, to start to understand it. Your explanation was sufficient, TNX. And the ::attribute way looks more reliable than using push and pull. Best, M. -------------------------------------------- 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
