mottelet wrote

Sven Gothel wrote

On 5/29/19 3:19 PM, mottelet [via jogamp] wrote:
> Hello, I am currently in charge of OSX version of Scilab, which uses JoGL
> (2.2.4) for a while now. There are currently two problems, one with Mojave
> (NSWindow drag regions shoud only be invalided in the main Thread) and the
> other one with Retina displays (tiny fonts and other glitches due to high DPI).
>
> I have downloaded the latest master build at
> http://jogamp.org/deployment/archive/master/gluegen_916-joal_642-jogl_1483-jocl_1122/archive/jogamp-all-platforms.7z and
> am able to build Scilab. Using JoGL 2.4.0 solves the NSWindow problem under
> Mojave, but the problem with Retina display remains. So my question is : since
> building with joGL 2.4.0 does not solve the DPI problem for Scilab, maybe do
> we have to change the way we use the joGL api ?

Please pick on of the High-DPI bugs (see wiki features for overview)
and create a new followup bug with detailed description
and best: small unit test.
I hope to be able to go through these dpi issues before the release
or shortly thereafter.

But to understand each scenario best, a small unit test attached
or via git patch would help most.

Thank you

~Sven

In the code where we create a GLJPanel I have inserted something to printout getMaximumSurfaceScale() and getMinimumSurfaceScale(). When I run Scilab both give me {1,1} regardless of the actual display hardware, Retina or classical DPI display. Should I obtain {2,2} on a Retina display ?