Hi Edgar,

Of course there are right now possibilites to recover changes from a hanging
squeak without having to resort to external tools.
First, and i think you know that, if the "hang" is just a one-off and you can
restart squeak you just use Changes->browse recent...
>from the world menu.
Second, if squeak hangs on restart and you have an exact ancestor of the squeak
image (the distribution image with which you started should be fine it just 
mustn't be a forked version or one that difers by a condense changes).
you can do the following:
Copy the ancestor image and the changes file respectivly and name them maybe
repair.[image|changes].
Fire up the image and do the browse recent change log thing.


At least this _should_ work.
On the other hand, it wouldn't hurt to have a tool that helps you out
finding stuff in change files belonging to dead image files.

HTH,
Torge

Am 06.11.2002 11:59:38 schrieb "Lic. Edgar J. De Cleene" <edgardec2001 at yahoo.com.ar>:

>Yoshiki:
>
> I found your image browser very useful.
>
>I wish beg you if possible add two features.
>
>1) What reading other image we can browse what classes are available,
> Actually if you don't know exact name of class , can't read nothing.
>
>2) One "rescue changes " feature. When I hang Squeak, I use Bbedit 5.0 (I
>have Mac, don't know equivalent soft in Windows / Lixux) for externally
>browse to end of file, and reverse find QUIT and SNAPSHOT from previous
>saves.
>Manually select lost code and copy / paste again in Squeak.
>
>If extending your code we can do recovering inside Squeak, sure many
>beginners like me send you VERY THANKS.
>
>Again , I wish You continue improving Squeak.
>
>Edgar
>
>Ahora podés usar Yahoo! Messenger desde tu celular. Aprendé cómo hacerlo en Yahoo! Móvil: http://ar.mobile.yahoo.com/sms.html
>
>