| For interactive use, ie. I sit at the
| octave console and type command for command invoking the callback there was
| sufficient. It's a question of taste on how you would like to update the symbol
| table: More updates means decreasing octave performance. I would opt in for
| performance. From a practical point of view, I might be interested in the
| current workspace when doing the following things:
|
| 1.) Working interactively at the octave console.
| 2.) Debugging a script, walking step by step and watching the workspace change.
|
| There is not need to update the symbol table model (which needs to be processed
| from the symbol table) too often.
I agree that it may not be necessary to update the list of symbols
that is displayed in the IDE every time it changes, provided that it
is updated "often enough". I'm just not sure what "often enough" is.
From a user point of view, I would consider it a bug it the variable browser was not in sync when octave is idle.
Just a simple example: you have a global variable, that is modified by some graphics callback. Not keeping track of the change would mean that, after triggering the callback, the user would have to press the Enter key in the octave console to see the variable updated (or pressing some hypothetical "Refresh" button in the variable browser). This doesn't sound very user-friendly.
Michael.