Hi Mark, first of all, thank you to you and Rony for your examples and workarounds.
I had just returned from a month away to a mountain of emails and was in a sort of despatch them quickly without thinking about them enough mode. Both methods look really good. I tend to code down grooves and I have used executeasynch in my code, but tended to think of it as only useful for splash screen type dialogs. You have opened up my mind a little and now that I see it it is obvious. As usual, you have put a lot of work into the example, for which I thank you. As far as backwards compatibility goes, it looks to me like I did something rather unorthadox here, and had I coded it sensibly it would work on 4.0.0. I'm not sure now who received advice from me on this, but I guess the same thing stands there, they have used the mechanism in a way that was not intended. It seems to me the onus is on us to rework our code to comply with intended usage of the tools. thank you for your help, Jon On 30 May 2010 17:23, Mark Miesfeld <[email protected]> wrote: > On Sat, May 29, 2010 at 10:25 PM, Sahananda (Jon) Wolfers > <[email protected]> wrote: > > > > I can't offer you much on this, but you ask > > > > On 28 May 2010 17:24, Mark Miesfeld <[email protected]> wrote: > >> > > ... > >> > >> 2.) This is not necessarily a bad thing, but it is different > >> behavior. Is it sufficiently different to be a problem? > >> > > > > and I would say that if I understand it correctly then it would > definitely > > cause me a problem. > > > > The old behaviour, although it feels wrong, has been a bit of a godsend > to > > me. Rexx\SQL can only work in the thread in which the library has been > > loaded. Therefore, where I want to access it in an oodialog method, I go > > through a rather hideous kludge of passing control to a method 'in' the > > original thread by programmaticaly editing a hidden edit control with a > > connecteditnotify watching it. > > Well, that's disheartening. > > My post wasn't really about the event handler methods running on a > different thread than the main thread, it never occurred to me that > people would write programs relying on that. (My other post has an > example program that doesn't rely on it.) > > The post is really about the behavior when there was a syntax > condition, or other condition raised in the event handler method. In > 3.2.0, this would normally print out the condition information and > cause the ooDialog program to end. Whereas in my current ooDialog, in > trunk, it would print out the condition information and the dialog > would continue to execute. > > What I was worried about was the difference in the program ending > versus continuing to run. > > What's disheartening is that I've spent a lot of time and effort > struggling to maintain backwards compatibility in ooDialog with what I > want to do / to implement in an improved ooDialog. It seems that, > that just isn't feasible. > > I'll probably post under a different subject heading to explore that > further. > > -- > Mark Miesfeld > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
