Difference between revisions of "Object Name"
(Created page with "==Scope== * '''Simulation''' project > ''action'' macro > '''Object Name''' property * '''Simulation''' project > '''Explanation''' macro > '''Object Name''' prope...") |
(→Scope) |
||
| Line 1: | Line 1: | ||
==Scope== | ==Scope== | ||
| − | * '''[[Simulation]]''' | + | * '''[[Simulation]]''' content object > ''action'' macro > '''Object Name''' property |
| − | * '''[[Simulation]]''' | + | * '''[[Simulation]]''' content object > '''[[Explanation]]''' macro > '''Object Name''' property |
==Purpose== | ==Purpose== | ||
Latest revision as of 19:30, 12 August 2019
Scope
- Simulation content object > action macro > Object Name property
- Simulation content object > Explanation macro > Object Name property
Purpose
This property specifies the name of the screen element (Control) with which the user interacts. This is typically captured during recording, but can be manually entered or changed, if necessary.
The contents of this property are typically inserted into the Demo Text or Practice Text during recording, or can be added manually via the $#{text_d} Placeholder.
For Explanation macros, this property is not captured - even if the Explanation was inserted into the project during recording, where it is necessary to click on a specific screen element. This is a throwback to earlier functionality whereby Explanation Bubbles could be anchored to specific screen elements in the same way that action Bubbles can. This functionality was discontinued long ago, presumably because of technical difficulties in making context capture consistently reliable for non-action macros. However, the availability of the Object Name and Object Image properties was retained, and these can be manually populated and then inserted into an Explanation Bubble in the same way that these same properties can be in an 'action' Bubble.
