Release Notes

Go Up to What's New

These Release Notes contain important information that might not appear in the main product documentation. We recommend that you read this page in its entirety.

If you are an active Update Subscription customer, see Subscription Update 1.

If you are an active Update Subscription customer, see Subscription Update 2.

Installing, Uninstalling, and Upgrading RAD Studio

Before you install, uninstall, or upgrade the product, read the following files, for your chosen language:

• radstudio_install_xx.htm: lists the system requirements, as well as installation and upgrade procedures.
• radstudio_license_xx.rtf: contains your Software License and Support agreement.
• radstudio_deploy_xx.htm: contains information about deployment.

Read the latest version of the radstudio_install_xx.htm file, available at the following locations:

• Installation Notes.
• The installation directory. The default location is: C:\Program Files (x86)\Embarcadero\Studio\18.0

Previous Versions and Migration

RAD Studio Includes Licenses for Previous Versions

Licenses for previous versions of the product are included with your Berlin license.

• Delphi Berlin includes licenses for Delphi Seattle, XE8, XE7, XE6, XE5, XE4, XE3, XE2, XE, 2010, 2009, 2007, and 7.
• C++Builder Berlin includes licenses for C++Builder XE8, XE7, XE6, XE5, XE4, XE3, XE2, XE, 2010, 2009, 2007, and 6.

For more information about licenses, see the radstudio_license_xx.rtf file in the RAD Studio installation directory.

Opening Projects Upgrades Them

When you open with RAD Studio Berlin a project that was created with a previous version of RAD Studio, RAD Studio upgrades that project. Upgraded projects do not work with previous versions of RAD Studio anymore.

Always create a backup of a project before you open it with a newer version of RAD Studio.

Upgrading from Delphi 7

If you are upgrading a project that was created in Delphi 7 or another early release, and the project has a custom file extension, you need to choose Project > Options > Application, and set the Target file extension to match the type of your project (.exe, .dll, or .bpl).

FireMonkey

Names Must Be Assigned to All Components Before Creating a New View in the Form Designer

If you open an older FireMonkey app in Berlin, you might encounter the following error message:

 Cannot inherit from form 'FormName".  It contains a component with a blank name property.

The new Views Inheritance system requires that you assign a name to all components before you can create a new View in the Form Designer.

iOS App Might Not Close/Reopen Properly After Running without Debugging on the Device

If you run your iOS app on the device without debugging and then kill the process of your application on the device, you will need to run the PAServer reset command if you want to run the process outside the IDE; type 'r' at the PAServer command prompt.

Web Browser Might Not Support Some Linking Behavior on Various Platforms

On a Web page that is displayed with TWebBrowser, when you click a hyperlink with the Target property set to "_blank" or "_search", you might encounter the following issues:

• On Android and iOS platforms, the application opens a linked page in the same TWebBrowser window.
• On Win32 and Win64 platforms, the application opens a linked page in a new Internet Explorer window.
• On the Mac OS X platform, clicking the links has no effect (the application cannot open the linked page).

FireDAC

Using Run-Time Packages with C++ FireDAC DataSnap Driver

If you use the FireDAC DataSnap driver in 64-bit C++ applications built with run-time packages, you might receive an error at run time. To avoid the error, you need to add DataSnapClient to the run-time packages, following these steps:

1. Project > Options > Packages > Runtime Packages.
2. In the Runtime package import libraries field, add DataSnapClient to the list.

This setting resolves the problem and adds DataSnapClient.bpi to the link line rather than DataSnapClient.a.

64-bit Windows C++ Application with a FireDAC Component Might Raise Error

The following error is raised when attempting to compile an application using a single FireDAC component, when the platform is Windows x64 with static linking:

c:\program files (x86)\embarcadero\studio\<n.n>\Bin\CodeGear.Cpp.Targets : warning : Warning: Out of memory
c:\program files (x86)\embarcadero\studio\<n.n>\Bin\CodeGear.Cpp.Targets(2751,5): error MSB6006: "ilink32" exited with code 2.

The workaround is not to link FireDAC statically in Win64 C++ apps.

Workaround for INI File Errors with FireDAC

In previous versions, FireDAC created INI files in "C:\Program Files", which in modern Windows versions is read-only for regular Windows users. If you are getting errors like "Can't modify file" when adding new FireDAC connection definitions using the Data Explorer or FDExplorer, then FireDAC INI files might still be located in "C:\Program Files". To resolve the issue, you should download and run the FDFixIni utility, which relocates the FireDAC INI files to a correct location and updates the FireDAC registry. By default, the correct location is "C:\Documents and Settings\All Users\Documents\Embarcadero\Studio\FireDAC".

To resolve the issue:

• download FDFixIni from the Registered Users site: http://cc.embarcadero.com/item/29812;
• extract the .EXE from the downloaded archive;
• and run it. If the utility runs successfully, it will output two lines with Move [old location] to [new location].

Box2D

RAD Studio Berlin does not provide prebuilt .dcu files for the Box2D.*.pas units.

• For Delphi projects using the Box2D.*.pas units, select Project > Options > Delphi Compiler, and update Search Path to include ${BDS)\source\FlatBox2D.
• For more information about using Box2D, see Box2D.

Android

Due to a bug of the Java Development Kit (JDK), the deployment path of a project must not contain non-ASCII characters for the Android target platform.

C++ Toolchains

Resolving Multiple Declarations for DWORD or ULONG in OS X Applications

In a multi-device application compiled for the OS X target platform, E2238 can occur because the OS X headers iodbcunix.h and sqltypes.h declare typedef statements for DWORD and ULONG, and the C++Builder sysmac.h file, which is included by System.hpp, also provides similar typedef statements. See E2238 for a workaround.

Specifying Dependent and Required Packages When Using a Component in a C++ Package

When using an existing component in a C++ package, the IDE does not automatically add the dependent (required) package for the component. You need to perform this step manually.

Without the relevant dependent (required) packages, the C++ package might fail to link because the linker cannot locate .obj files that must be initialized when that component is used. To avoid such linker errors, you need to add the package of the component and its dependencies to the Requires node of your C++ package (in the Project Manager).

The following example illustrates how to determine the required packages for a component and eliminate the Unable to open 'xxx.obj linker errors by creating a dummy VCL Forms Application that uses the component.

By default, a newly-created C++ Multi-Device Application links with the .rtl and .fmx packages, as shown by the *.bpi files listed on the linker line (viewable in View > Messages):

Ilink32 command line:

 c:\BDSLoc\bin\ilink32.exe ... -aa -V5.0 -Tpe  c0wfmx32w rtl.bpi fmx.bpi memmgr.lib sysinit.obj .\Win32\Debug\Project30.obj .\Win32\Debug\Unit26.obj , .\Win32\Debug\Project30.exe , .\Win32\Debug\Project30.map , import32.lib cp32mti.lib , , Project30.res

When you add new components, the IDE calculates dependent packages and adjusts the link line. To see this, add the component you want to use in a C++ Package to the Multi-Device Form. This example uses the component TFDSchemaAdapter. Now rebuild the application. You will see that several new .bpi files have been added to the link line:

Ilink32 command line:

 c:\BDSLoc\bin\ilink32.exe ... -aa -V5.0 -Tpe  c0w32w rtl.bpi fmx.bpi FireDACCommonDriver.bpi FireDACCommon.bpi xmlrtl.bpi dbrtl.bpi FireDAC.bpi FireDACSqliteDriver.bpi memmgr.lib sysinit.obj .\Win32\Debug\Project30.obj .\Win32\Debug\Unit26.obj , .\Win32\Debug\Project30.exe , .\Win32\Debug\Project30.map , import32.lib cp32mti.lib , , Project30.res

These new .bpi files are the packages on which your component depends. In the case of TFDSchemaAdapter, the .bpi files are:

   FireDACCommonDriver.bpi FireDACCommon.bpi xmlrtl.bpi dbrtl.bpi FireDAC.bpi FireDACSqliteDriver.bpi

So to use the TFDSchemaAdapter component in a C++ Package, you need to explicitly add each one of these bpi files as 'Required' references in the IDE (see Packages (Delphi)).

Downloading DirectX Header Files

We only ship DirectX headers inside the Microsoft Windows Platform SDK. If you encounter errors such as "d3d.h file not found", the HPP generated for that Delphi unit contains #include <D3D*.hpp>. You can do either of the following:

• Add a {$NOINCLUDE Winapi.D3DX9} directive to the unit that uses the D3D unit and regenerate the HPP file of that unit. The regenerated HPP will not contain the #include <Winapi.D3DX9.hpp>.
• Download the DirectX SDK that the D3D header relies upon. You can download the DirectX SDK for free from Microsoft. For more information, see Where is the DirectX SDK? (Windows).

Events with Structures or Sets of 5-8 Bytes Are Not Valid for BCC64

Events generated by the IDE that take a struct or set that is between 5 and 8 bytes are valid for 32-bit C++, but not valid for 64-bit C++. This only affects cases where the type is passed by value. For cases where the type is passed by reference, there is no difference between Win32 and Win64.

For example, an Access Violation occurs when accessing the TPoint &MousePos parameter of the OnContextPopup event, because the TPoint &MousePos parameter is invalid on the Win64 platform. If you look at the __closure type declaration, you can see the difference between Win32 and Win64. Here is the __closure declaration for the PopupMenu event of TControl:

#ifndef _WIN64
typedef void __fastcall (__closure *TContextPopupEvent)(System::TObject* Sender, const System::Types::TPoint &MousePos, bool &Handled);
#else /* _WIN64 */
typedef void __fastcall (__closure *TContextPopupEvent)(System::TObject* Sender, System::Types::TPoint MousePos, bool &Handled);
#endif /* _WIN64 */

To get the code to work for both Win64 and Win32, you must #ifdef the IDE-generated handler as follows:

#ifndef _WIN64
void __fastcall TForm46::FormContextPopup(TObject *Sender, TPoint &MousePos, bool &Handled)
#else
void __fastcall TForm46::FormContextPopup(TObject *Sender, TPoint MousePos, bool &Handled)
#endif
{
  ShowMessage(System::String().sprintf(L"Mouse at (%d,%d)", MousePos.X, MousePos.Y));
}

Exception Handling with Optimization Options for BCC64

Using the BCC64 compiler with the optimization option -O2 enabled might cause exception handling issues. You can disable this option under Project > Options > C++ Compiler > Optimizations. See C++ Compiler Optimizations for more detail about optimization options.

This option does not apply to RAD Studio Berlin Subscription Update 1.

IDE

In the Multi-Device Form Designer You Can Only Delete a Component from the Master View

When you try to delete a component, such as a TButton, from a different view (not the Master view), the following error message appears:

 Selection contains a component, Button1, introduced in an ancestor and cannot be deleted

The solution is to delete the component from the Master view. For more information about views, see Form Designer.

Renamed iOS Project Might Fail at Run Time or When Debugging

Renaming a project in the IDE can cause an iOS app to fail at run time and debug time. To correct the issue, do the following:

1. Select Project > Deployment.
2. In the Deployment Manager, click the Revert To Default speed button.

Version Info Settings Inheritance

To include version information in a project targeting Windows, do not change the key values on the All Platforms target. Instead, change the values individually for each platform (32-bit and 64-bit). The targets do not inherit the values properly from the All platforms target.

InterBase

InterBase XE7 Edition Accompanies Some Editions of RAD Studio Berlin

This note pertains to users who have both an earlier version of RAD Studio and RAD Studio Berlin installed on the same machine. In this note, the mention of RAD Studio also implicitly includes Delphi and C++Builder editions.

Each version of RAD Studio includes a license for a version of InterBase:

Product	InterBase Version
RAD Studio XE3	InterBase XE3 Developer Edition
RAD Studio XE4	InterBase XE3 Developer Edition
RAD Studio XE5	InterBase XE3 Developer Edition
RAD Studio XE6	InterBase XE3 Developer Edition
RAD Studio XE7	InterBase XE3 Developer Edition
RAD Studio XE8	InterBase XE7
RAD Studio Seattle	InterBase XE7
RAD Studio Berlin	InterBase XE7

Since all these RAD Studio license suites are visible system-wide, only one license of InterBase can be used at any time.

For example, if you are running the "InterBase XE3 Developer Edition" that comes with RAD Studio XE6, you cannot start a simultaneous instance of the "InterBase XE3 Developer Edition" that comes with RAD Studio XE7. You cannot start a simultaneous instance of the InterBase XE7 edition that comes with RAD Studio Berlin either. When you try, you receive an error dialog that states "InterBase licensing error", and the InterBase log shows "Registration file error: License is in use by another instance of InterBase".

For more information about running multiple instances of InterBase, see Multiple Instances section in http://docs.embarcadero.com/products/interbase/IBXE7/OpGuide.pdf.

Workaround for InterBase Licensing Errors

1. Stop all your instances of InterBase.

   Also, if you have set up this instance as a Windows Service, please disable it in the system Service Control Panel.

2. Start the instance of InterBase that you want to use. It should now launch successfully with the proper license.

The aforementioned earlier RAD Studio versions, and applications built by them, can also work with the updated InterBase XE7 edition installed with RAD Studio Berlin. Have your older IDE tools and applications connect to your database via TCP loopback to this InterBase instance. For example:

localhost/gds_db:<dbpath>

In older versions of RAD Studio, you might also want to select Tools > Options > Environment Options > Environment Variables and add the following new "User overrides" entries for making local client connections.

Variable	Value
IB_Protocol	gds_db
InterBase	C:\Program Files (x86)\Embarcadero\Studio\18.0\InterBaseXE7

External Software

Issues might occur for applications debugged in an environment that includes a third-party keyboard switcher such as the Yandex Punto Switcher. If the application is closed by Windows, and an access violation is raised by the application, please ignore this access violation error.

See Also

• Installation Notes