WindowImpl has a default position of 64,64
This caused a misaligned mousepointer and window
seen on the Raspberry Pi.
By overriding the default position to 0,0
we can workaround the issue for some use-cases:
We have analysed the bug and proposed ways to properly resolve it in the jogamp irc channel
(01:46:07) sgothel:  hence optional clamping of the position state (x, y) in the LinuxMouseTracker - used by bcm to clamp to screen size
(01:46:45) sgothel:  our native bcm moveTo code shall reduce the dest-rect to avoid further artifacts (explicit clipping)
(01:47:14) sgothel:  our java bcm window code shall validate pos and size to not exceed screen size
Clamp window position and size to 0/0 and screen-size,
avoiding out-of screen window positions on BCM VC IV hardware
Out of screen window positions on BCM VC IV hardware cause:
- Misalignment of self-rendered mouse-pointer / window
due to window-offset.
- Artifacts when moving the mouse pointer partially
out of screen.
We still need to add the window position to rel. mouse-pointer position.
Add window-position to window-relative mouse position in
Refine clamping of window position and size at native creation
- Refines commit a566a1b5a2828b38f1a5c4dfb215ab9b03e7acaa
- Issue clamping at 'canCreateNativeImpl()' instead of 'createNativeImpl()',
allowing to define clamped position and size before utilizing these values
at caller 'createNative()'.
Otherwise a clamped position would cause to wait for the original position
This also allows to remove the positionChanged(..) / sizeChanged(..) calls in
the native CreateWindow0() implementation.