TCL History lost (OpenInsight 64-bit)
At 11 DEC 2023 04:56:50PM BrianWick wrote:
On rare occasion OI 10.2.0 crashes - for example if i stop a TCL report using the esc key - it askes if i want to close the program… and i do.
however - I lose all the tcl history upon logging back in.
does that have to happen ?
tx
Bri
At 20 FEB 2024 07:18PM Robert Heard wrote:
Hi Brian,
Yes, this has been an annoying "feature" if you <Break> and get to the debugger and then type "Q" to quit. It does a HARD logout rather than a SOFT logout, whereby it would do all the normal logout stuff like saving the TCL command stack.
I have found that when I start a process for the first time and there could be a fault along the way, before I run this new program, I will logout and back in again so that my TCL history gets saved and then I run the program.
There is probably a better way to save the TCL command stack, but don't know what this is (yet).
Robert.
At 22 FEB 2024 04:01PM BrianWick wrote:
Hi Robert -
I have been doing that.
But when I log back in all the TCL history is still there.
But if I have a hard stop for whatever reason all the TCL history sill is gone.
tx
for the ideas anyway
Bri
At 23 FEB 2024 04:16AM Andrew McAuley wrote:
The stack is written back on logout and crashing avoids that. Maybe drop a suggestion in the box that the stack be updated on the editline CHANGED event rather than the window close?
World leaders in all things RevSoft
At 25 FEB 2024 07:40PM Robert Heard wrote:
Hello Brian,
Surely when you say "all of the history is gone", you don't mean that when at TCL and you press <F2> that the list is empty. You mean that all the commands you issued in the current session were lost, right?
My experience is that if AREV32 does a hard crash and drops straight out, back to the OI Application Manager screen, then only the commands in that latest session (from when I last logged in), are lost, because the LOGOUT routine did not get the chance to run.
It would be handy to have a command that may be used to simply "updaate" the Command Stack. I have tried "RESETSYSTEM" and "RESET" (equivalent), but this does not seem to save the command stack. Not really sure what the RESET command does. Can someone explain this please?
Robert.
At 25 FEB 2024 09:23PM Barry Stevens wrote:
Hello Brian,
Surely when you say "all of the history is gone", you don't mean that when at TCL and you press <F2> that the list is empty. You mean that all the commands you issued in the current session were lost, right?
My experience is that if AREV32 does a hard crash and drops straight out, back to the OI Application Manager screen, then only the commands in that latest session (from when I last logged in), are lost, because the LOGOUT routine did not get the chance to run.
It would be handy to have a command that may be used to simply "updaate" the Command Stack. I have tried "RESETSYSTEM" and "RESET" (equivalent), but this does not seem to save the command stack. Not really sure what the RESET command does. Can someone explain this please?
Robert.
RESET (from a tattered AREV COMPANION – Chesapeake computing - RIP Dave)
At TCL level 1 RESET reloads the environment and video settings, resets the system variables, reinitialises status bar, repaints backdrop, loads default macro key set.
If RESET is executed from other that level 1 of TCL, it reinitialises the current windows an repaints the status line ONLY
At 26 FEB 2024 10:39AM BrianWick wrote:
Yes -
the TCL History is gone after a hard crash.
It sounds like the answer comes from what andrew mentioned.
Every time a command is executed from TCL - at that time it needs to first save the TCL stack - then execute the command - which currently is not the case.
tx guys
bri
At 26 FEB 2024 05:32PM Robert Heard wrote:
Thanks Barry,
Wow, big difference on how it behaves.
All my applications begin with a Menu. How can I run anything in TCL at Level 1?
Robert.
At 28 FEB 2024 10:14AM Andrew McAuley wrote:
World leaders in all things RevSoft