> On Fri, Dec 28, 2012 at 7:29 AM, Art Heimsoth > <artst...@artheimsoth.com> wrote: > >>> On Thu, Dec 27, 2012 at 8:01 PM, Art Heimsoth >>> <artst...@artheimsoth.com> wrote: >>> >>>>> On Thu, Dec 27, 2012 at 3:50 PM, Art Heimsoth >>>>> <artst...@artheimsoth.com> wrote: >>>>> >>>> Okay, this also appears to be working except for when I >>>> attempt to execute a method from the OK method in the child. >>>> I am using SQL in the child InitCode method okay, and a log >>>> method in the setup of the data, where the log method is in >>>> the mother and the execution of it is in the child method >>>> (someMethod) in your example. Those both work okay. When I >>>> attempt to execute the same log method from the OK in the >>>> child, the dialog seems to not respond anymore until I "X" >>>> out of the child dialog. >>>> >>>> >>> Which dialog doesn't seem to respond? The parent or the child? >>> >> The parent is blocked and beeps when attempting to click on >> anything within it. The child accepts the Ok click, but nothing >> happens until I cancel it with the windows "X" - then all the >> pending actions for the Ok method continue. >> > > The reason it will block when you press ok is that the parent > dialog is executing in the onTest() method, which is guarded. The > log() method in the parent dialog is also guarded. > > So when you invoke log() in child dialog's ok() method, the log() > method can not run, because it is guarded and can not gain access > to the dialog's variable pool. It can not run until the onTest() > method finishes. > > > A simple change that fixes this is to make log() unguarded. > Okay, is there a place where the actions of guarded (which I assume it the default) and unguarded are relative to a method? From your description here, in my words, guarded/unguarded is dealing with serialization of the dialog's variable pool, where if a method is guarded, no other method can gain access to the variable pool for that dialog and will be blocked when another method is started within that same dialog. Also the execute() will keep the containing method active until the executed dialog ends. Is this correct and are there other implications of using unguarded; ie, are any variables protected from modifications performed by other methods while a given method is unguarded and active?
I have never understood the guarded/unguarded operation and do not know the rules for usage. Thanks again for your great teaching help. I really appreciate it. -- Art Heimsoth - artst...@artheimsoth.com ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
