Dear P.O.:
On 08.08.2017 12:43, P.O. Jonsson wrote:
> I cannot help you finding the cause of your problem but I can try to run the
> program on various
> machines and collect some stats.
Thank you very much!
> I have downloaded the complete kit and can launch startTestProgressBar.rex
>
> I can
Dear Rony,
I cannot help you finding the cause of your problem but I can try to run the
program on various machines and collect some stats.
I have downloaded the complete kit and can launch startTestProgressBar.rex
I can see that the rexx program launches Java and the GUI show up with 3
Dear René:
On 07.08.2017 17:10, René Jansen wrote:
> Memory in multihreaded programs should be strictly guarded.
AFAIK I am doing that everywhere in BSF4ooRexx.cc (cf. e.g. RgfAcquireLock()
and RgfReleaseLock()).
> I know of a few debuggers that can set memory modification watches/traps, one
>
Memory in multihreaded programs should be strictly guarded. I know of a few
debuggers that can set memory modification watches/traps, one is OS/2’s kernel
debugger and the other is MVS’s SLIP SET trap mechanism. From what I see
sometimes the register save area is clobbered (assuming you are
One hint: after installing BSF4ooRexx one can use the menu "BSF4ooRexx ->
Samples" to get an
explorer window. Then changing into "JavaFX" and loading "index.html" will
explain how to run those
JavaFX nutshell examples. You will see why I think it is so important to get
the JavaFX support
stable
After intensive further experimentations today, on one occasion I got the
following
runtime-popup-error, if this matters:
---
Microsoft Visual C++ Runtime Library
---
Debug Error!
Program: C:\Program Files (x86)\ooRexx\rexx.dll
