Known Issues and Limitations

This section provides a list of known issues and limitations in the ACT 18.2 release.

Graphic API Issues in DesignModeler and Mechanical when No Extensions are Loaded

There are some limitations on the Graphic API in Mechanical and DesignModeler when no extensions are loaded. For instance, the Factory2D does not work. It is therefore advised to have one or more extensions loaded prior to the usage of the Graphic API.

Launching the ACT Start Page on Linux can cause an unexpected shutdown

For a given configuration, launching the ACT Start Page on Linux causes an unexpected shutdown. Because this problem cannot be duplicated on testing machines, a problematic configuration rather than a code issue is suspected.

Localization Support Limitation

Localization of ACT is limited to the languages currently supported in ANSYS Workbench. This limitation does not apply to the ability to manage various languages within the extension. For example, the property names created by an extension do not have to be in the same language as the current activated language in ANSYS Workbench.

There is no mechanism to integrate localization for the property names defined by an extension. To manage different languages for your property names, you must develop localization yourself. Both regional settings based on the "." or the "," decimal symbol are available. However, the implementation of the extension should use the "." symbol for any value defined at the XML or IronPython level.

Automation API UI Thread and Performance

When you are using the ACT automation API, automation methods and properties must be called in the UI thread. Before 18.1, error messages or unexpected shutdowns were the potential results of the call of the automation API from a callback that was not executed in the UI thread.

As of 18.1, this issue is solved by automatically redirecting every call to the automation API in the UI thread. While you will no longer experience error messages or unexpected shutdowns, automatic redirection can potentially decrease performance. Poor performance is most likely to occur when you repeatedly call the automation API many times, such as when looping through nodes. If you notice a significant decrease in performance, you can speed up the process by using one of the following commands to bypass the multiple switches to the UI thread:

  • ExtAPI.Application.InvokeUIThread(func, arg) // This executes the function func with the argument 
    arg in the UI thread.

  • ExtAPI.Application.InvokeUIThread(func) // This executes the function func in the UI thread.

A usage example follows.

def get_all_object_names(name_list):
    """ Returns the given list populated with all the names of the objects in the tree. """
    for obj in ExtAPI.DataModel.Tree.AllObjects:
        name_list.Add(obj.Name)
    return name_list

name_list = list()
all_object_names = ExtAPI.Application.InvokeUIThread(get_all_object_names, name_list)


Important:  Due to technical reasons, the namespace of the automation API object has changed. Therefore, you should not use the method GetType() as a way to verify the nature of the object that you have. Instead, you must use the property DataModelObjectCategory, which is available on all objects. It returns an enum value indicating the type of the object. For example, the following command returns true:

ExtAPI.DataModel.Project.DataModelObjectCategory == DataModelObjectCategory.Project


Release 18.2 - © ANSYS, Inc. All rights reserved.