RAD Studio 10.2.2 Tokyo February 2018 Patch » Developer Team :: Best choice for developers!

RAD Studio 10.2.2 Tokyo February 2018 Patch

RAD Studio 10.2.2 Tokyo February 2018 Patch
RAD Studio 10.2.2 Tokyo February 2018 Patch

This patch for RAD Studio 10.2.2 (build 2004) resolves some compatibility issues in the RTL and fixes a problem with Android animations. It is designed to be installed only on top of an existing RAD Studio 10.2.2 Tokyo installation.

This patch resolves the following issues:

- 10.2 Tokyo Release 2 breaks Animation under Android - App hangs (RSP-19525 and additional animation and TabControl animation issues, including the duplicate items RSP-19537, RSP-19585, RSP-19564, and RSP-19555)
- 3rd party components compatibility with the HTTP Client Library (a subset of the cases covered in RSP-19529, which were not already fixed in build 2004)
- Direct call to inet_pton (ws2_32.dll) broken on Windows XP (RSP-19836)
- TFDIBSecurity.DisplayUsers has a memory leak (internal bug)

Last week, Embarcadero released a patch for Tokyo 10.2.2, focused on Android and RTL improvements. What happened is that Windows would not always ask for execution with admin account (on systems with active User Account Control) and could end up copying the replacement files in a wrong location. It did affect a few of the developers who tried it, so we pulled it, fixed the installer and now re-issued the patch.

If you are a registered user of Tokyo (or have a license for it), you can find it at https://cc.embarcadero.com/item/30819.

There is no change in the content on the patch, so if you already installed it successfully, there is no need to repeat the process. On the other hand, if your installation got broken, we have provided an alternative ZIP-based option (in the same download page). We have already sent it to developers who had got in trouble, but might not have reached everyone.

As for the content, the main fix is the Android animations and tab animation issue. These have been addressed. There are still cases in code where the combination of called to Application.ProcessMessages and timers might get you in trouble. I'll blog more information ASAP, but the general recommendation is to use threads rather than timers for background processing -- an all platforms, although in Windows that coding style can be used.

Updated Notice: Only for 10.2.2 Build 2004
We had a notice in the download page, but better repeat it here. The patch is only for the second build of 10.2.2 we released, build 2004. If you have the previous build (which had compatibility problems with third party packages) don't install the patch. Either wait for a future update (if you don't specifically need the fixes the patch provides) or install build 2004 first. The link to 2004 installer is in the patch download page.

Only for V.I.P
Warning! You are not allowed to view this text.

Users of Guests are not allowed to comment this publication.