Thanks Mark, yes this is on XP. Am I creating another problem if
I always use unguarded on my methods, whether they are events
or others?
I am having other problems in my main program that I suspect are
due to the usage of unguarded or lack of. I have an input panel
with several edit input fields where I am using LOSTFOCUS and also
GOTFOCUS on some of them. I have unguarded on all of those event
handlers, but if I cancel out of that input panel, I sometimes get entries
into one or more of those event handlers - like the event is pending
somewhere when I do the cancel and start a different menu process.
I don't know how to cancel the events when the original input menu
is cancelled, and some of them will put up more info on the screen
when they fire.
> To fix that, you need to make either ok() or logError() unguarded.
>
Will change these two. Thanks again.
>
> Things shouldn't crash though. Is it on XP you see the crash?
--
Art Heimsoth - artst...@artheimsoth.com
--
Art Heimsoth - artst...@artheimsoth.com
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
