[Sticky] Astro Pixel Processor 2.0.0-beta29 release notes

Astro Pixel Processor 2.0.0-beta29 release notes

• Updated development platfrom to Oracle GraalVM JDK 21.0.2+13.1

  This update has several critical patch updates for all platforms as can be found here: https://www.oracle.com/java/technologies/javase/21-0-2-relnotes.html

• Updated FITS READ/WRITE dependency to nom.tam.fits 1.19.0 - fixes read-only access to FITS on network share
  

  Our dependency to read and write FITS files has been updated to 1.19.0. This version has an important workaround for handling read-only FITS files on Windows network shares. See here for more info: https://github.com/nom-tam-fits/nom-tam-fits/releases/tag/1.19.0

• macOS native FILE/DIRECTORY Chooser

  The native File/Directory chooser is now the default again instead of the development platform File/Directory chooser. The reason for this is that the native chooser only has 1 downside, CMD-A does not work still, but it has many more positives when compared to the platform chooser, CMD -> to expand folders works, it really has macOS look and feel, it is much easier to access/find networks shares or external drives on macOS.

• FIXED macOS Apple Silicon OpenGL bug with images larger than 1,5GB

  As reported in this topic https://www.astropixelprocessor.com/community/main-forum/image-viewer-crashing-beta-20/#post-28460 the OpenGL image viewer crashes on Apple Silicon macs when the image data is larger than 1,5Gbytes. The crash does not occur in the code of APP, but in a native library of macOS for OpenGL support. This native library is used by our OpenGL dependency to provide OpenGL support on Apple Silicon macs. So this fix is now a workaround where we prevent the application from crashing and show the image with the CPU image viewer. We need to wait for our OpenGL dependency JOGL to fix this or perhaps we even need to wait for Apple to fix this in their OS.

• FIXED FITS SAVER issue with NaN/Infinite header values

  If you would save a file in the FITS format with header values that are NaN or infinite, APP would have stopped with a bug. This is fixed, the data will still be saved, and the user will get 1 warning about a possible data issue, because the header values should never become NaN nor infinite. The issue was reported in this thread:  https://www.astropixelprocessor.com/community/main-forum/fits-header/#post-30122

• FIXED APPLICATION CLOSE ON macOS with CMD-Q

  As reported in this topic: https://www.astropixelprocessor.com/community/macos/register-tab-defaults-to-mosaic-no-matter-how-many-times-i-reset-defaults/ APP would not be closed properly if you use CMD-Q to close APP on macOS. CMD-Q is the macOS application close shortcut. This is now fixed. When you use CMD-Q, the application will now be closed properly, including saving of all settings.

• FIXED Null Pointer Exception in xxxFitsConverter

  In some corrupt fits files, the fits kernel can't be read and this occured in this NPE. We have now properly caught this issue and the user will be warned that a certain file is probably corrupt. Issue was reported here: https://www.astropixelprocessor.com/community/main-forum/sixteenbitsfitsconverter-error/#post-29569 and here https://www.astropixelprocessor.com/community/windows/encountered-error-in-modulesixteenbitsfitsconverter/#post-30283

• FIXED ArrayIndexOutOfBoundsException in FrameDataCalibration/LightFrameCalibration

  As reported in this topic  https://www.astropixelprocessor.com/community/main-forum/jave-error-when-beginning-a-new-session/#post-29314 an ArrayIndexOutOfBoundsException could occur when monochrome and OSC/color masters were mixed with calibrating monochrome or color light frames. This exception will no longer occur, and the data will be calibrated with the masters loaded. It would occur if the masterbias had a CFA pattern in the fits header and the masterdark would not have a CFA pattern in the header.

• FIXED license activation with wrong character encoding

  Every license code starts with 2 letters: Ow(ner), Re(nter), Tr(ial) followed by 4 sequences of 4 digits separated with a - character. This - character can sometimes cause problems with license code input if the license code was not stored in UTF-8 character encoding. For instance, users on windows would store their code in a pdf or word document with a microsoft character encoding. When they copy-paste the code into APP, the - character, all of a sudden, is no longer the correct - character, which would then report that the license code is not valid. This problem has been fixed on both the license-server side and in the Astro Pixel Processor application as well. You can now enter the license code with an arbitrary separator instead of the - character and the code will be accepted, provided that the letters and digits are all correct of course. The input for the letters is case insensitive as well. For example, let's suppose a user has license code : Tr-1111-2222-3333-4444 and he/she enters tR{1111%2222##33334444, the code will be accepted and will be reported in the LICENSE menu with Tr-1111-2222-3333-4444 still. So that means that you can also leave out the separator character completely, so the user could also simply enter tr1111222233334444 and it will work. In versions prior to beta29 the entered code will be shown as the user entered it in the LICENSE menu, so in this last case, the LICENSE menu would show license code tr1111222233334444 instead of Tr-1111-2222-3333-4444. With beta29, the correct format will be always shown in the LICENSE menu when the license was activated with beta29 as well.