On Mon, 30 Jun 1997, Chris Kelly wrote:
> I have had the same experience. I posted a few messages a while back about
> lost bindings. I have found that if you have vtcl in "edit" mode when you save
> you never lose bindings, but in "test" mode you might. I have never found a
> consistent pattern except that (as I recall) only toplevels which had not been
> opened during a given vtcl session would lose their bindings. Further, if you
> save in "test" mode the display continues to say "test" but the toplevels act
> like they're in "edit" mode. It becomes necessary to cycle between modes to
> get "test" mode to work again.
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.
> I agree that vtcl needs to be perfect in terms of code loss. It still have a
> very "edge of the seat" feel to it. Like Rick, I make backups every time I
> edit. It will still lose entire toplevels over something as simple as a
> unavailable font, or any kind of simple syntax problem in the gui code.
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-
