Rick Macdonald wrote:
> Something used to happen to me where errors would occur when I saved my
> application. ...
..
> I manually make copies of my application every time I edit it. When I get
> up to maybe 20 backups I start deleting some old ones.
>
> I've been saying for some time now that vTcl has to be bullet-proof when
> it comes to not loosing one's work or people won't use it for long.
>
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.
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.
Chris Kelly / TRW SIG
