Jerry,

Thanks for reminding me of that issue. I've planned for a long time to
remove the "auto-select-Squeak.XXX.image" feature in favour of the strategy
"select the image automatically if there is only one and present a file open
menu otherwise". I'll fix it for the release VM.

Cheers,
  - Andreas

> -----Original Message-----
> From: JArchibald at aol.com [mailto:JArchibald at aol.com]
> Sent: Monday, February 05, 2001 5:13 PM
> To: Raab, Andreas; squeak at cs.uiuc.edu
> Cc: JArchibald at aol.com
> Subject: Windows VM 3.0 default .image name?
> 
> 
> Andreas--
> 
> The Windows VM has, for some time, presented a selection of 
> the available 
> .image's when there is more than one in the folder containing 
> the VM. I have 
> gotten in the habit of keeping a number of workspaces 
> (.image/.changes pairs) 
> in that folder with (relatively) descriptive names. I noticed 
> a change in 
> behavior in the 3.0 VM which you just released.
> 
> The new semantics seems to be: (1) if there is only one 
> .image file (of any 
> name) in the VM folder, load that one, (2) if there is an 
> image in the VM 
> folder with name 'Squeak3.0.image', load that image, (3) if 
> there is an image 
> with the name 'Squeak.image', load that image, else (4) 
> present a dialog box 
> with the available .image files. (There may be other 
> possibilities, but no 
> other image name that I chose would do other than (4) -- in 
> particular, 
> 'Squeak3.1alpha.image' was not a special name).
> 
> My questions are: (1) Are there other "built-in" image 
> names?, and (2) Are 
> the constants defining these "identifiable" images available 
> in the image 
> (and thus can be accessed), or are they part of the VM itself 
> (and cannot be 
> accessed)?
> 
> Thanks,
> Jerry.
> ____________________________
> 
> Jerry L. Archibald
> systemObjectivesIncorporated
> ____________________________
>