• 델파이와 C++빌더 XE2 업데이트 3가 발표되었습니다.


에 가보시면 XE2 업데이트 3에 대한 내용이 있습니다. ^^

아래는 내용입니다. 영어...입니다... ^^;;;

Release Notes for XE2 Update 3

Go Up to What's New in Delphi and C++Builder XE2

This file contains important supplementary information that might not appear in the main product documentation. Embarcadero Technologies recommends that you read this file in its entirety.

This document refers to "the product" when the information applies to RAD Studio XE2 or to either or both of the two personalities: Delphi XE2 and C++Builder XE2.

For general information about installation, deployment, and licensing, see the Install, Deploy, and License files located, by default, at C:\Program Files\Embarcadero\RAD Studio\9.0. On a Windows 64-bit system, the directory is Program Files (x86).


Installing this Update

Delphi and C++Builder XE2 Update 3 is an MSI-based patch. This update can be applied over any of the following products:

  • Delphi XE2 with Updates 1 and 2
  • C++Builder XE2 with Updates 1 and 2
  • RAD Studio XE2 with Updates 1 and 2

You can install this update in any of the following three ways:

Upgrading via the Automatic Upgrade Mechanism

If you selected "Check for Updates Automatically" when you installed the product, you should automatically be notified when an update is available for download.

Click the notification and follow the instructions to download and install the Update.

Manually Checking for Updates

If you do not receive an automatic notification about the update, you can check for updates manually:

  1. Select Start | Programs | Embarcadero RAD Studio XE2 | Check for updates.
  2. In the list of available updates, select RAD Studio XE2 Update 3.

Downloading from the Registered Users Web Page

Update 3 is also available for download from the registered users download pages as follows:

Download <RADStudioXE2Update3.zip> to your computer and extract the zip file to install the update.

Note: This update process might take fifteen minutes or more to complete. You should avoid stopping the Update installation once it has started.

Uninstalling this Update

If you need to uninstall the update, you must uninstall the entire product and reinstall the RTM build. It is not possible to uninstall only the update.

General Notes

Bug List

For a complete list of the specific problems fixed in this update, see the "List of Bug Fixes in Delphi and C++Builder XE2 Update 3" at:http://edn.embarcadero.com/article/41831/

FireMonkey Styles

A new style has been added for FireMonkey: Light.Style. In addtion, the iOS.Style has been modified to be compliant with iOS UI guidelines. iOS.Style is the default style for FireMonkey iOS applications. The FireMonkey styles that are provided with the product are located in C:\Program Files\Embarcadero\RAD Studio\9.0\Redist\styles\Fmx. For more information about FireMonkey styles, see Customizing FireMonkey Applications with Styles.

C++ Applications that Do Not Use VCL Forms Should Not Include <vcl.h>

That is, applications (such as console, database, or Web/SOAP applications) that do not use the GUI elements of the Visual Control Library (VCL) should not specify:

#include <vcl.h>

The <vcl.h> header includes all of the VCL Forms library, as well as the Delphi RTL.

If you want to use Delphi types (such as System.Set<>System.Variant, or System.UnicodeString) in a non-visual C++ application, do either one of the following:

  • Specify:
    #include <System.hpp>
  • Include the appropriate unit that declares the types and API you want to use. For example:
    #include <Classes.hpp>
    #include <SysUtils.hpp>

For more information, see Using Include Files.

In previous versions of C++Builder, the wizards, code examples, and application samples often used <vcl.h> as an easy way to access funtionality exposed by the Delphi RTL package. However, C++Builder XE2 (and newer versions) must be able to distinguigh among UI frameworks (VCL vs FMX) and Target Platforms (Windows vs OSX).

Therefore, we recommend that you update all non-VCL code that includes vcl.h to instead include the appropriate header from the RTL, SOAP, Database, or other specific package. You can implement this by creating a precompiled header that includes the RTL headers required by your code. You might create, for example, <myheaders.h> that in turn includes the various RTL headers such as Classes.hpp, SysUtils.hpp, and so forth.

Changes to ModalResult Values for TButton (both VCL and FMX)

At the XE2 release we introduced three new ModalResult values for VCL TButton and for FMX TButtonmrContinuemrHelp, and mrTryAgain.

In addition, four of the existing ModalResult values changed. If your applications use any of these four ModalResult values for TButton, you might need to make code changes. That is, the values have changed for mrClosemrAllmrNoToAll and mrYesToAll. Since the values are stored as numbers in .dfm files, the values change when you migrate a project to XE2.

The ModalResult values have changed as follows:

  • Before XE2:
    • mrClose=11
    • mrAll=8
    • mrNoToAll=9
    • mrYesToAll=10
  • In XE2:
    • mrClose=8
    • mrAll=12
    • mrNoToAll=13
    • mrYesToAll=14

Thus the results are as follows:

XE Modal Result   XE2 Modal Result   









For complete information and solutions, see "XE2 values of mrAll, mrNoToAll, mrYesToAll and mrClose" at http://www.bobswart.nl/Weblog/Blog.aspx?RootId=5:5029

    • 백록화
    • 2012.07.03 13:42
    • /
    • 류종택
    • 2012.07.03 16:24
    • /
    • 이정욱
    • 2012.01.06 20:38
    • /
    • 이정욱
    • 2011.12.31 22:51
    • /
    • 명태
      2012.01.06 10:43
      새해 복 많이 받으시고 하시는일 모두 잘 되시길 바래요~언제나 감사 합니다.. ^^;
    • 심즈
      2012.01.17 17:37
        회원님들.. 늦었지만 새해 복 많이 받으세요.^^ 올 한 해 부자되세요^^
    • 이정욱
    • 2011.12.04 19:03
    • /