Sorry, I'm not interested in getting that involved with this again. I will
answer specific questions about how the code works, but that's the limit. I
will NOT get involved in directly debugging these issues.

Rick



On Wed, May 10, 2017 at 1:33 PM, Rony G. Flatscher <[email protected]>
wrote:

> Rick, would it help, if I created a zip-archive to download with
> directions how to start the Rexx
> application (using JavaFX)? If so, please let me know which bitness you
> would need for the
> bsf4oorexx.dll (pre-requisite is that you have Java 1.8 installed). Also,
> I can make the 32- and
> 64-debug versions of ooRexx (from today's trunk with your fix for the
> memory leak applied)
> available, either as an NSIS installer or as a zip-archive of the
> bin-directories.
>
> This might allow you to better debug the cause with Visual Studio or the
> like. It is strange that
> this application causes different errors it seems, depending on the
> bitness of the debug version of
> ooRexx.
>
> ---rony
>
> P.S.: All other JavaFX samples work flawlessly with the patched version.
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to