Next: LIBLINCKS Functions
Up: Command History
Previous: Logged Commands
Because the command history is stored as ordinary objects in the
database, it is accessible to the user and could therefore be edited
by him/her which is a problem. The command history should not be
directly viewable, since the paradigm is that you can edit everything
you see. This is done by adding a link in the system root history
structure node. Users can not access any history structure node. That
link, called `CH:History', is an unbound link to the ch object.
The user history object where the attributes function and type always have
a value, the others are dependent on the command type.
- CALL:Function The name of the command (Attribute).
- CALL:Type Database or workspace command (Attribute).
- CALL:Application What application executed the command (Attribute).
- PARAMETER:From Function parameter (Attribute).
- PARAMETER:To Function parameter (Attribute).
- PARAMETER:Group Function parameter (Attribute).
- PARAMETER:Field Function parameter (Attribute).
- PARAMETER:Position Function parameter (Attribute).
- PARAMETER:Lbl Function parameter (Link).
- PARAMETER:From Function parameter (Link).
- PARAMETER:To Function parameter (Link).
- CH:Prev_command A set of bound links that points to the
preceeding database commands.
The command history object, ch object:
- CHNET:Front A pointer to the latest executed command (Link).
Martin Sjolin
Thu Jun 15 20:41:59 MET DST 1995