Posted by
Sven Gothel on
Feb 06, 2020; 9:49am
URL: https://forum.jogamp.org/Frame-with-transparent-background-tp4040332p4040340.html
On 2/6/20 10:27 AM, gouessej [via jogamp] wrote:
> Ok. Why not filling a bug report against Oracle Java?
>
> In my humble opinion, it might be a limitation of Java2D OpenGL pipeline which
> was implemented earlier than the public API for translucent windows (the
> private API for that is a lot older, see AWTUtilities).
>
> You claim that it's a simple case but it requires a lot of complicated source
> code to access to some native APIs to produce the expected behavior.
>
> Have you tried "-Dsun.java2d.trace=log"? If so, what does it mention?
>
> "-Dsun.java2d.opengl.fbobject=false"?
and ..
On 2/6/20 10:37 AM, gouessej [via jogamp] wrote:
> It's a known concern:
>
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6655001>
> We'll need to disable HW acceleration (both OpenGL and
> D3D pipelines) for non-opaque windows on systems other
> than Vista.
Great digging Julien.
Yes, it is a complicated not well supported experimental
feature. AFAIK AWT and Swing is hardly supported these days.
Complicated due to side effects and not specified implementation
of the renderer backend - even though it did its job quite well.
This is the same criticism I throw towards OpenJFX,
blackboxing the renderer by intention does not allow others
to benefit from it and maintenance for 3rd parties is hard.
Hence my 'long sighted' proposal for OpenJFX to utilize
NEWT and JOGL (OpenGL or Vulkan) for the OpenJFX backend
<
https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20>
This is how we had it in the earlier days ;-)
~Sven