Bug report. Collision between the name of the property and API function

[MimiKLM]

Recently I came accros situation like that:

I have a local container called AAA with the subproperty called "Name".

Then I'd like to change the name of the AAA container using the API function ".Name".

However, when I call Local.AAA.Name, instead of changing the name of AAA container I'm accessing the subproperty with this name.

I think the name "Name" should be reserved as a name of subproperty.

[dug9000]

You can still access the name API property as follows:

Locals.AAA.AsPropertyObject.Name

The "API in expressions" feature was not in TestStand originally, and thus there are backwards compatibility implications if we were to either make it give precedence to API properties or to disallow using a name that conflicts with an API property. Thus the current behavior of TestStand is to give precedence to the subproperty when there's a conflict with an API property, and by using AsPropertyObject a user can still access the API property if needed.

I do think the AsPropertyObject workaround needs to be made more obvious though. It does not show up in the list when you type '.', but it does work.

Hope this helps,

-Doug