What's New with APIs in Autodesk Design Review 2011?

Design Review Software Engineer, Herbert He, mentions a few noteworthy changes to the 2011 Design Review APIs that aren't included in the current API documentation.

• New Animation Detection API
• New Lighting and Field of View Commands
• Moved APIs

New Animation Detection API
This new API enables you to detect if the 3D section as an animation section. This would be useful if the client code needs to control whether the animation commands are shown, or to provide some other feedback to the user based on the presence of animation.

EModelSection2.HasAnimation Property
Query whether the 3D section has animation.

Syntax
object.HasAnimation

Return Values
Return code Description
S_OK The property was retrieved successfully
E_INVALIDARG Invalid parameter passed
E_FAIL Current section is invalid

Remarks
If the 3D section has animation object, the value of the property is VARIANT_TRUE, else the value is VARIANT_FALSE.

New Lighting and Field of View Commands

Lighting Commands:
Two lighting commands were added in order to provide a more simplified lighting interface to the user (others were removed from the UI but are still available in the API). These new simplified lighting commands are available in the API.

1. NOLIGHTING
An additional possible value for EModelSectionType2.LightingOption, "No Light".
2. DEFAULTLIGHTING
An additional possible value for EModelSectionType2.LightingOption, "Default Light".

Field of View Commands:
Two field of view commands were added to allow the user to increase or decrease the field of view.

1. FOVWIDE
Only applicable to 3D sections, increase the value of field of view by 5 by default. For example:
 CompositeViewer.ExecuteCommand ("FOVWIDE");
   or
 CompositeViewer.ExecuteCommandEx ("FOVWIDE", 0);

2. FOVTELEPHOTO
Only applicable to 3D sections, decrease the value of field of view by 5 by default. For example:
 CompositeViewer.ExecuteCommand ("FOVTELEPHOTO");
   or
 CompositeViewer.ExecuteCommandEx("FOVTELEPHOTO", 0);

Moved APIs from the EPlotRenderer interface to the EPlotViewer interface

As a result of refactoring the Autodesk Design Review code base, all COM objects were removed from the EPlotRenderer module, relocating all EPlotRender APIs to the EPlotViewer module.

All existing code such as:

EPlotRenderer.IAdPage*
  and
 EPlotRenderer.CAdPage*

…needs to be changed to:
 EPlotViewer.IAdPage*
  and
 EPlotViewer.CAdPage*

Thanks for the update Herbert!

Comments

[Ketul Patel]

Hi using ADR APIs is it possible to extract Mark-ups from one file and Add it to another, I am trying to build something that will allow to see a consolidated view of mark-ups from different users, I can see Markup amd MarkupEditor objects in the API but could not find any documentation on how to use them?

[Leland Leahy]

They used to have a way to restore a Named view. Does anyone know if that still exists?

[granit tezgah]

mark-ups from different users, I can see Markup amd MarkupEditor objects in the API but could not find any documentation on how to use them?

[Danny DeMichele Entrepreneur]

I am trying to build something that will allow to see a consolidated view of mark-ups from different users.

[Challenger parts]

Its nice they provide some other feedback to the user based on the presence of animation.Thanks