• Cima under svn. file locations, rebuilding, etc
  
•  Cima home page

Cima problems:

• fixed azimuth drift pattern close to the ao lattitude does not behave as expected.
  

Cima Outline:

Storing program state frontend:

Interactively modifying state:

• Copy state hash (eg mock()) to setup() hash.
  
• All the keys,values of mock() copied to setup()
• set mock(trace) no  to disable tracing during this move.
  
• Interactive menus modify values in setup($keys)
• When done, the program copies the setup($keys) back to mock($keys)
• set mock(trace) no  to disable tracing during this move.

• the menu buttons, entries, selections modify the setup($keys) values
• A variable trace is set on each key in setup() for writes to setup()
  
• trace_variable setup($key) check_mock_configuration
• checks all the setup($key) variables each time anyone is modified.
  
• trace_variable setup($key) check_current_mock_variables $w
• this check to see if there are any differences between setup($key) mock($key)

• some menu selections vary depending on other variables.
• You need to update the menu selection options since the program verifies that each selection is a valid menu value.
  

• check_menu_option setup($key) $status  (procedures.tcl)
• goes through and makes sure that values in setup($key) are valid menu button values.
  
• valid_menu_value $setup($key)
  
• see if global variable menu_valid_value() contains $setup($key)
• set_up_menu() (menubuttons.tcl)
  
• set_menubutton()  loads the values when menu defined.
  
• change_menu_list() can be used to modify the values after the menu is created.
  

home_~phil