Posted by Sven Gothel on Jul 26, 2012; 6:02pm
URL: https://forum.jogamp.org/NewtCanvasAWT-resize-bug-tp4025658p4025664.html

On 07/26/2012 05:43 PM, Job Zwiers [via jogamp] wrote:
> I noticed that after resizing a NewtCanvasAWT Canvas to height = zero, the
> application cannot be terminated anymore without using the Windows 7 task
> manager. I checked this with builds 785, 636, 571. With an older build (417,
> august 2011) everything works fine.

We sure handle a zero sized component (NEWT, NewtCanvasAWT)
as a non realized drawable - at creation time.
Good that you report this behavior, since I haven't validated
the resize to zero behavior with an already realized drawable.
Problem: On some platforms a zero drawable surface is invalid.

Can you describe your test case a bit more in detail ?
I assume you setup an arbitrary NewtCanvasAWT as shown in your snippet
and _manually_ attempt to resize it to zero ?
Can you attach a log file w/ all debug flags enabled ?
(See wiki page .. -Djogl.debug=all -Dnewt.debug=all -Dnativewindow.debug=all;
redirect stdout/stderr to one file [bash test.sh > a.log 2>&1] and attach it)

> Also, I did not notice any problem with
> Newt without using NewtCanvasAWT.
That reduces the error space, thx. Still, we have to
validate our behavior here as well.

> Any ideas?

Guess we are working on this together here.

~Sven