Set JAWTWindow:reqPixelScale before the DPI scaling factor is determined and fix AUTOMAX_PIXELSCALE #112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Set JAWTWindow:reqPixelScale before the DPI scaling factor is determined, so if GLCanvas.setSurfaceScale() has been called, the correct 'reqPixelScale' is available. It's possible to call GLCanvas.setSurfaceScale() before JAWTWindow has been created. Fix feature AUTOMAX_PIXELSCALE so the requested pixel scale is used.
I discovered the NASA WorldWind was setting reqPixelScale immediately after GLCanvas was created. The code in JAWTWindows ignored 'reqPixelScale' when setting up the 'hasPixelScale' value. I surmise that AUTOMAX_PIXELSCALE was intended to all a user to set the surface scale with the GLCanvas.setSurfaceScale() call, which sets 'reqPixelScale' These changes allow the override of using 'maxPixelScale' to set 'hasPixelScale'.
The call to GLCanvas.createJAWTDrawableAndContext() is made when the first GLCanvas.addNotify() call is made. The JAWTWindow is created, and JAWTWindow.lockSurface() causes the DPI scaling value to be determined in JAWTWindow.updatePixelScale().