Visual Interface Xecute Shell
Brought to you by:
ferret1964,
twiechmann
Menu
▾
▴
#70 Visual Interface Xecute Shell
I'm using 'EsiObjects Visual Development System
Professional Edition Version 4.0.1, Build 8' and
EsiObjects Server GTM Linux version 4.1.0.7.
When I startup the visual environment with /Admin
or no parameters, select an object anywhere in the
tree, and then use Alt-X to open the Xecute Shell, it
always opens in the Environment object context.
However, if I start the visual environment using
the /ESI command-line parameter, then it works as
described in the documentation (i.e. if I Select the
Person object under Party in the Tutorial library, the
Xecute Shell correctly starts under the
Tutorial$Person context).
Logged In: YES
user_id=84471
The documentation in the Administrators guide is correct but
incomplete and will be enhanced shortly. The system is
responding correctly. In /Admin mode, your actions should
put you in the $ENV object context. It is the default.
In /Debug mode, the Xecute shell will come up in the context
of the selected object for debugging purposes. However,
in /ESI mode (combination of both), the /Debug overrides
the /Admin mode and the Xecute Shell will come up in the
context of the selected object. If an object is not selected, it
will come up within the $Env object context.
Logged In: YES
user_id=615127
Sorry - my misunderstanding.