Re: [Oorexx-users] Deadlock in guarded method - ooDialog or me?

[Mark M. <mie...@gm...>]

On Tue, Mar 15, 2011 at 2:31 PM, Dave Dawson
<da...@dr...> wrote:
> There’s NO multitasking going on in my program, but I have a couple of
> multitasking related problems.

Windows is a multi-tasking operating system, so there is always
multi-tasking going on in any program running on Windows.

> Are there any known problems in the beta so far relating to either “deadlock
> detected” or user routines simply stopping dead waiting for resources
> belonging to other user classes?

Yes.  What version of the beta are you using?  I'm been refreshing the
beta builds about once a month.  The latest is from around the end of
February / first of March.  If you are using the first version I put
up, then you definitely need to get the latest.

If you have the latest version, then please read the section in the
docs on coding event handlers.  5.7.1 in particular.  Also look at 5.7
and 2.2.4.

Plus, can you let me know if you do or don't have the latest version.

> One quick example …
> ...
> Putting a “trace I” just above the problem line gives this output from the
> 2nd call of setuppupilcombo
...
> And this is where the trace pauses until I end the dialog, then the trace
> continues, trying to add the relevant pupils to the combobox.

It's hard for me to tell exactly where the problem is here.  Is it at
all possible for you to send me the complete program so I can look
into this?  Just mail it to me at my gmail address miesfeld at
gmail.com.

> Back to the main point – my problem or a problem with oodialog?

Either or both.  <grin>

Try the latest version of the beta if you have the first version, and
let me know.  If you already have the latest version, try making the
pupils attribute unguarded and let me know if that fixes the problem.
Otherwise, the easiest way for me to see where the problem is would be
to send me your program.

Thanks for bringing this up.

--
Mark Miesfeld