Can I suggest that it should really be made a primitive to decide at startup
the correct depth to start at? In fact I assumed that is what it did.

The statement "very few people have their OS display depth set to 16
bits..." sounds a bit dodgy to me seeing Squeak is run on many different
systems and at least some are old equipment.

Of course you need to do this quickly so how about the compromise of:

SomeClass (not sure where)>>initialDisplayDepth

	<non-existent primitive>
	^32

That is used to load the preference unless its overridden.

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org [mailto:squeak-dev-
> bounces at lists.squeakfoundation.org] On Behalf Of Doug Way
> Sent: Thursday, 17 June 2004 2:58 PM
> To: The general-purpose Squeak developers list
> Subject: Re: Default UI preferences for 3.7
> 
> 
> On Wednesday, June 16, 2004, at 09:05 PM, Raymond Asselin wrote:
> 
> > Le 2004/06/16, Doug Way <dway at mailcan.com> écrivait :
> >
> > Hi Doug,  I think we should go with 32 bits for the display depth,
> > don't
> > you ?
> 
> Good point, I'll add that one to the list.  Offhand, I'd say yes, we
> should switch to 32 bits.
> 
> Pros:
> - Better rendering of colors, of course
> - Faster graphics performance for most, because most people will have
> their OS display depth set to 32 bits, and performance is usually best
> when the Squeak depth matches the OS depth
> 
> Cons:
> - For those who have their OS display depth set to 16 bits, Squeak
> might show up as a black screen if the Squeak depth is 32 bits. (I've
> seen this on some platforms, anyway.)  However, these days very few
> people have their OS display depth set to 16 bits...
> 
> - Doug
>