This document includes any important or open issues you need to be aware of in a specific product.
Double Byte Characters cannot be displayed using cout on windows XP. |
Due to a problem in the C++ Visual Studio 2005 SP1 compiler, some messages using double byte characters cannot be displayed using cout. This issue is described on support.microsoft.com in KB entry number 927753, on compiler RTM level. No MS patch is available for now on SP1 level, but the description of the KB describes two possible workarounds. |
Documentation search "Find next" command fails with Internet Explorer 7 |
The "Find next" command fails when used after searching the CAA
Encyclopedia with Internet Explorer 7 with a red popup stating "netscapejavascript.JSException". This command enables you to successively find the different occurrences of the searched string in the opened file from the Search result window. |
CAA Media Content Changes |
In order to help customers' and partners' applications comply with the CAA V5 usage rules described in the CAA Encyclopedia, our offering is refined by better aligning the CAA build time media content with the CAA Encyclopedia content. Thus, starting with V5R15, non-CAA Authorized APIs previously located in the ProtectedInterfaces folders are no longer available from the CAA build time media. While enriching the CAA Authorized APIs offering with new CAA APIs matching new needs, we will continue to deliver with CAA RADE a more and more secure development environment by protecting CAA applications from the risks of using non-CAA Authorized APIs. As a reminder, CAA RADE tools prevent the usage of undocumented resources located in ProtectedInterfaces starting with V5R12. In some cases, the CAA RADE tools may not have detected all uses of the non-CAA authorized APIs. To ensure that all non-CAA Authorized APIs have been detected, CAA RADE provides an audit tool. Launch it before attempting to build your CAA applications. Please refer to the What's New in the CAA Encyclopedia for further information on how to use this audit tool. Please contact your local support if you need assistance. |
Locating Documentation and Use Cases |
You can access the CAA Encyclopedia online documentation with a HTML browser at
the following addresses: <CATIA, DELMIA, or ENOVIA CAA APIs installation path>/CAAV5HomePage.htm> or <CATIA, DELMIA, or ENOVIA CAA APIs installation path>/CAADoc/Doc/online/CAACenV5Default.htm> |
ENOVIA Search does not find all customized objects |
When working on an ENOVIA VPLM customization based on several workspaces concatenation, the ENOVIA Search gives only access to customized objects defined in the first workspace of the concatenation. Customized objects defined in the other workspaces are not found.
Bypass: 2 cases can occur
|
None |
Using CAA-RADE Data Model Customizer |
|
Icons and/or Commands might not be displayed with RADE Tools using Visual Studio 2005 |
If icons and/or commands are not displayed in the menus:
If a command is still missing in the menus, proceed as follows:
|
CAA Add-ins might not be correctly loaded with RADE Tools using Visual Studio 2005 |
If the CAA add-ins are
not loaded:
|
CAA Shortcuts are not correctly working with Visual Studio 2005 |
Some CAA shortcuts may not work correctly with Visual Studio 2005. For example, Ctrl+T will transpose characters. CAA commands are assigned to the "Global" domain of use instead of the "Text Editor" domain. To fix it, redefine the domain of use of the shortcut, as follows:
|
None |
None |
None |
|
None |
CAA Samples/Applications That Can't Execute on AIX with non US Locale Settings |
On locales other than English (en_US) on the AIX Operating System, you can
get following error messages on standard output/error when executing a CAA
sample or application:Can't open library libTheViewLibrary.a --> reason = A file or directory in the path name does not exist or: Could not load program MainExe: Could not load module libShared_1.a. Dependent module Shared_2.exp could not be loaded. Whereas the library exists and is accessible from the application. In the case the command /usr/bin/dump -H on the impacted library shows an invalid dependency on an export file, such as: dump -H libShared_1.a INDEX PATH BASE MEMBER 0 /lib:/usr/lib 1 libJS0GROUP.a 2 Shared_2.exp The problem may be caused by unexpected collation order in non English locales. Problem was reported with German locale setting (de_DE), but other locales may be impacted. To workaround this problem, you should:
You can also add the export of the environment variable at the end /usr/DassaultSystemes/B18/aix_a/code/command/mkinit.sh |
CAA Samples/Applications That Can't Build in Debug Mode on Solaris |
Building CAA samples or applications in debug mode (mkmk -g) on Solaris may fail due to additional links to unauthorized symbols added by the Solaris C++ compiler. |
Multi Workspace Application Builder doesn't support anymore LINK_WITH cards that includes the module extension
|
Up to V5R15 included, the following syntaxes were equivalent in Imakefile.mk files:
or
they were both requesting link-edit against module myModule.m. Starting in V5R16, the first syntax is not supported anymore because, as mkmk now supports module names with multiple dots, like for example:
it is so not able anymore to understand whether myModule.m stands for module myModule.m or myModule.m.m. |
Build time control of usage of non Authorized CAA APIs does not work on Windows 64-bit. |
RADE Multi Workspace Application Builder does not perform checks on usage of non Authorized and deprecated CAA APIs on Windows 64-bit. Take care to also build your code on a Windows 32-bit platform to be sure not to use non supported APIs. |
None |
|
None |
None |
None |
|
None |
None |
None |
|
None |
None |
None |
|
None |
None |
Using Implementations of Specs Modeler Interfaces |
A new MkCheckSource error (VISI) detects the usage of prohibited implementations of Specs Modeler interfaces. An example is the CATSpecObject class. You are invited to check this error, and modify your code to use the appropriate interface in place of the internal class. For example, do not use CATSpecObject, but instead use the interface that CATSpecObject implements and that supplies the CATSpecObject method. In this release, without this migration, your code could fail. |
None |
None |
None |
|
None |
None |
None |
|
None |
None |
Mappings tab page is displayed empty |
The Mappings tab page that allows you to define data mapping between the different data sources (widgets, Session Data, Web Methods, custom-written java code ) is displayed empty. |
None |
CAA C++ and VBScript/VBA Applications are not supported in a Small Scale session. |
Small Scale is a capability
available since V5R18
that allows to create geometry in a new geometrical range with a
submicron precision. This capability has the following constraints:
Due to the complexity involved by those constraints, V5R19 Small
Scale sessions will not support CAA applications: |
Compilation error when using windows afx windows APIs in CAA V5 modules |
The following message may be issued
when using afx windows APIs within a CAA V5 module:
This is due to modifications in base CAA header files aimed to
improve build performance and reduce debug files size. The recommended
solution to solve this problem is to create a file called
|
Inter release compatibility of VB/VBA macros |
Please note that existing VB/VBA projects may require manual adjustments to be usable on a new release. Consult the Automation documentation article "About VB, VBA, Debug, and Portability" for more information. |
Session freezes when displaying a customer defined contextual menu. |
The session freezes when trying to display a contextual menu associated to an instance of class CATDlgTableView. Is is recommended not to use this functionality in CAA Applications until it is corrected. |
CAA Authorized APIs Are in PublicInterfaces |
The CAA authorized C++ , Java, and IDL APIs are located in the
PublicInterfaces directories of the exposing frameworks.
CAA authorized APIs:
As a rule, never use other APIs from the PublicInterfaces directories. APIs from header files located in the PublicInterfaces directories that include the CAA Tag @CAA2Level L0 at the top are beta-authorized APIs. They are not intended to be used in your applications, except for tests. They are neither build time stable, nor run time stable, and can disappear without previous notice. |
Using CAA Interfaces with a PDM Product |
Since V5R7, when using the implementation of the CATIDocEnvironment interface of the ObjectModelerBase framework, the CATIA Team PDM license is checked and the methods fail if no license is found. |
Warning C4251 on Windows |
When using the Multi Workspace Application Builder with -g option,
the Microsoft Visual Studio 2005 compiler produces a lot of C4251
warnings concerning CAA APIs, like for example:CATMoldDesignUI\PublicInterfaces\CATMldComponentDlg.h(1005) : warning
C4251: 'CATMldComponentDlg::_hSurf1ToComputeCompAxis' : class 'CATSurface_var'
needs to have dll-interface to be used by clients of class 'CATMldComponentDlg' Denoting possible link-edit problems when using the CATMldComponent
class. There is no such problems in V5R19 CAA APIs, so those warnings, when
issued on CAA APIs, can be safely ignored. Those warning can also be
filtered out by adding to the Imakefile.mk of the client
application modules the following cards:OS = win_b64 This will also filter out similar warning issued on the client application code, possibly hiding real problems, but such problems would appear at link-edit anyway. |
Warning 4995 at compilation |
The following warning appears at compilation:
It is due to a Windows deprecated pragma. It can be ignored. |