Leaderboard

Because only 1 patch has been released so far. And that was for 12.0, not for 12.1. Correct. Point releases usually require a full uninstall and reinstall. You can't do that with Getit from within the IDE (but the installer uses GetIt technology). Patches can update an existing installation, so it makes sense that they can be distributed via GetIt. You can login to your account at https://my.embarcadero.com to download the 12.1 installer. Feel free to file a feature request at https://qp.embarcadero.com

From the official docs: Given that FMX Android apps are served as native code I suspect this change could mean something that Embarcadero should check carefully. Luckily the same page offers links on how to test an app on a 16 KB environment (emulator), so I did with a blank FMX app and... libc Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7d7f34f39000 in tid 5935 Yes, the app crashes at startup, but it works on a non-16 KB emulator. Maybe is too early to tackle this problem yet (no 16 KB devices on the wild afaik), but given that this change could be complex (update NDK?) and take a while (Delphi 13?) I hope there is something devs can do to fix this on our own with what we have at hand (i.e. Delphi 12.x). As a side note I tested this on an Android emulator running on a Mac with M2 chip as ARM emulation is no longer possible on Windows.

The installer will uninstall anyway. No way around that yet. 3rd party components might survive the uninstall, or not. Make sure to click the save settings box when prompted at the uninstall part of the procedure, that helps a lot.

Slightly off topic: Reading this site with the standard light layout I thought the images where all broken...until I saw the webp and realized all images are white on transparent background. Silly me

If there is a new patch / version available it will always show up in this forum. This is how I get informed 🙂

If there is a new version or patch for the IDE, it also will show up on the Welcome page.

I don't use FMX and I haven't looked at the source but as far as I can tell, from your the images and description, the problem is that TBitmap premultiplies on load and unpremultiplies on save. The degradation of pixels with alpha<>255 is caused by the inevitable rounding errors. The VCL TBitmap has the same problem if one messes with the AlphaFormat property. Apparently they didn't learn from their first mistake and instead decided to make it worse. The reason the FMX TBitmap premultiplies the bitmap is probably because it needs that when displaying the bitmap (e.g. when using the Win32 AlphaBlend function). Anyway, the solution to your problem is to not use TBitmap as a storage container. Use TBitmap only for display of the image and use instead use TMemoryStream or something like it for storage.