Was this in a fresh session?

I have experienced that behavior when running the code after other
opengl code had been running.  In some cases, that was because 'sprog'
existed, and represented a shader that I was not prepared to feed. But
it's quite possible that there's some other issues where I am assuming
a fresh opengl context and that's not what I am working with.

If this was in a fresh session, however, (or, if you are really
interested in finding the interaction issue) I might have to ship you
a opy with a bunch of debug logging type statements, to determine
where it's shutting down.

Thanks,


--
Raul


On Tue, Feb 8, 2022 at 5:22 PM Brian Schott <[email protected]> wrote:
>
> I just now tried again.
> I copied the code from rosettacode.org into the clipboard and then used F8
> key to paste the code. I had done the same last time. But this time J quits
> ("unexpectedly") immediately without a graphics window appearing, or if it
> does appear, it disappears so fast I could not see it.
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to