> aha. I think that's the little nugget of gold we were looking for. I can
> now envision a problem when saving in "test" mode. I've never actually
> tried this. For now, my recommendation is don't do it.
>
> when in test mode, bindings are temporarily restored. vtcl should force
> the app into "edit" mode before saving. I'll put together a patch against
> 1.10 tonight that does this.
>
The reason I save in test mode is because I am changing procedures and
testing repeatedly. vTcl doesn't seem to have control of the application in
the way that a typical debugger does. As a result, if I create an endless loop
in a tcl procedure or lock up in one of my c++/Fortran core routines vtcl will
lock up as well and any changes are lost. Because the Fortran code I'm using
is buggy I need to save a lot.
>
> 1.11 will change the way apps are stored during edit so this type of
> situation cannot occur (i.e. typos in code, fonts, etc).
>
> -stewart-
>
Will 1.11 do anything about this problem?
Chris Kelly / TRW SIG
--- End Forwarded Message ---
