next up previous contents index
Next: LIBLINCKS Functions Up: Command History Previous: Logged Commands

Command History Objects

       

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.

  1. CALL:Function The name of the command (Attribute).
  2. CALL:Type Database or workspace command (Attribute).
  3. CALL:Application What application executed the command (Attribute).
  4. PARAMETER:From Function parameter (Attribute).
  5. PARAMETER:To Function parameter (Attribute).
  6. PARAMETER:Group Function parameter (Attribute).
  7. PARAMETER:Field Function parameter (Attribute).
  8. PARAMETER:Position Function parameter (Attribute).
  9. PARAMETER:Lbl Function parameter (Link).
  10. PARAMETER:From Function parameter (Link).
  11. PARAMETER:To Function parameter (Link).
  12. CH:Prev_command A set of bound links that points to the preceeding database commands.
 

The command history object, ch object:

  1. CHNET:Front A pointer to the latest executed command (Link).
 



Martin Sjolin
Thu Jun 15 20:41:59 MET DST 1995