Assign alias to variables.
Is there some way to assign Aliases to global variables in scripting so that you can update them in one file when the Aliases is changed between software revisions. This can change if they cleanup the...
Forum Discussion
Hi Andreas,
While technically it is possible to do what you are asking for, the better approach is to assign textual representation of the alias to some public variable (defined as per your scripting language requirements) and use this variable where needed using eval/evaluate function (again, as per your scripting language) to resolve the text to actual object.
E.g. something like that (pseudo-language, untested):
var lblNavigationInfo = "Aliases.application.wndQwidget.QWidget.Statusrow.frmMain.framebox_2.lbl_navigationPath";
...
if (eval(lblNavigationInfo + ".Exists"))
Regions.Compare("lbl_NavigationTest", lblNavigaionInfo);
else
Log.Warning(lblNavigationInfo + " was not found");
However, the beauty of aliasing is that you can define the tree of aliases as per your needs (see relevant help topic for how to organize the tree of aliases) and then, with properly defined NameMapping (i.e. with the use of Extended Find, Conditional NameMapping and Configurations (again, see the relevant help topics for mode details)) you will not need to edit the tree of aliases when the nameMapping scheme changes, but only to adjust the nameMapping tree leaving Aliases as they are.
While technically it is possible to do what you are asking for, the better approach is to assign textual representation of the alias to some public variable (defined as per your scripting language requirements) and use this variable where needed using eval/evaluate function (again, as per your scripting language) to resolve the text to actual object.
E.g. something like that (pseudo-language, untested):
var lblNavigationInfo = "Aliases.application.wndQwidget.QWidget.Statusrow.frmMain.framebox_2.lbl_navigationPath";
...
if (eval(lblNavigationInfo + ".Exists"))
Regions.Compare("lbl_NavigationTest", lblNavigaionInfo);
else
Log.Warning(lblNavigationInfo + " was not found");
However, the beauty of aliasing is that you can define the tree of aliases as per your needs (see relevant help topic for how to organize the tree of aliases) and then, with properly defined NameMapping (i.e. with the use of Extended Find, Conditional NameMapping and Configurations (again, see the relevant help topics for mode details)) you will not need to edit the tree of aliases when the nameMapping scheme changes, but only to adjust the nameMapping tree leaving Aliases as they are.