Posted by Sven Gothel on Apr 18, 2023; 7:49am
URL: https://forum.jogamp.org/intent-of-reqPixelScale-in-GLCanvas-tp4042430p4042467.html

Goal was and is to flatten platform differences, at least in the top public APIs. Here its the semantics of whether the surface-size will be scaled (MacOS) or if its fixed and hence the window coordinates have to be scaled (Windows, Linux).

Additionally, the general semantics are a bit odd and on Windows + Linux sort of reverse (like Matrix multiplication).
So this naturally adds to the confusion.

Other API abstractions we have are AFAIK not that difficult to my knowledge, or at least they are mostly straightforward.

Hmm, I saw no issue with the NEWT mouse pointer API when integrated it with GraphUI, we did that somewhat together back then AFAIK - consolidating touchpad + mouse to multi-pointer.

But of course, complexity is high when changing something in-between the public API and the platform-code, as side-effects are always possible and auto-testing certain UI feats are hard, especially interaction.
For the latter I used AWT-Robot and our own 'mouse control -> warp' .. still, its a big thing.

Hence hacking now on general simple UI layout and math is a breeze :)

But I will come back to this to fix it .. and I am glad that we have other testers like you here.