Profile objects for different presentation engines

Create dynamic links between Boolean properties of objects and the {Session}/IsNative and {Session}/IsWeb aliases. You can then display different objects using different presentation engines.

Tip: Download a sample project: ProfileObjects.zip
Figure 1. Native presentation engine and Web presentation engine.

This example shows an application that displays two different objects based on the presentation engine.

Prerequisites

To profile objects for different presentation engines
  1. In Project view, select an object to profile.

    For example, select a rectangle.

  2. In Properties, create a dynamic link between a Boolean property and either:
    • Aliases > {Session} > Session > UI Session > Native session
    • Aliases > {Session} > Session > UI Session > Web session

    For more information about dynamic links, see Create dynamic links.

    For example, create a dynamic link between the Visible property of the object and Aliases > {Session} > Session > UI Session > Native session to make the object visible in the native presentation engine only.

  3. In Project view, select an object to profile.

    For example, select another rectangle.

  4. In Properties, create a dynamic link between a Boolean property and either:
    • Aliases > {Session} > Session > UI Session > Native session
    • Aliases > {Session} > Session > UI Session > Web session

    For more information about dynamic links, see Create dynamic links.

    For example, create a dynamic link between the Visible property of the object and Aliases > {Session} > Session > UI Session > Web session  to make the object visible in the native presentation engine only.

The native presentation engine and web presentation engine display different objects.