From: steve@dcdwest.uucp (Steve Meloche)
Subject: Re: PageStream V2.2--Problem w/ selecting screen colors
Organization: ITT Aerospace/Communications Division - West
Distribution: na
Date: Wed, 8 Apr 92 01:17:25 GMT

In article <56991@cup.portal.com> soft-logik@cup.portal.com (Kevin W Davidson) writes:
>>
>>147/150: Screen colors tutorial
>>Name: Gumby #1 @13459
>>Date: Fri Mar 13 20:39:34 1992
>>
>>There still continues to be some confusion over screen colors and related 
>>problems.
>>
	.
	.
	.
A quoted description of how Pagestream chooses colors was here...
	.
	.
	.
>>- IF there is only one "gray" color in the screen colors, then both Black    
>>objects (normally text), and White objects (the page) map to this color.
>>
	.
	.
	.
>>What some folks have done because of the flicker, or just because they wanted
>>different colors, is changed the colors to something else which they find mor
>>pleasing. Whether this is a leftover PgS2.1 PSPrefs file, or a changed PgS 2.
>>WB2 screen colors, if they have less than two "gray" colors by the above 
>>definition, they have both Black and White mapping to the same screen color. 
>>This means that text will not be visable on the page!  If there is only one 
>>"gray" and it is 100% White, then the page and the TEXT will be white.  If th
>>only "gray" is totally Black, then the text and the PAGE will be black!  This
>>is the way it is suppose to work!  Its NOT broken.  Please tell anyone who is
								   ---^---^---^		?!?!?
>>reporting a Black page, or text does not show up on screen, to make sure that
>>they have atleast TWO "gray" screen colors by the above definition.
>>
>>Mike K.
>>

Many things about 2.2 are much improved over previous versions of the program,
and PageStream is still a very nice, useful program.  I would like to take
issue with the above statement, however.  In my humble opinion, if this
particular scheme for choosing screen colors was intentional, then it was just
an error in judgement.  It is totally *absurd* to make both black and white map
to the same pallette color, *ever*.  I don't care at all if the color is "hue
neutral" that is used for text, as long as I can *read* it!  With 1.7, 1.8 and
2.1 I used a sort of beige (paper) and dark-brown (black) color scheme to
virtually eliminate flicker.  With Pagestream 2.2's OS2.0-like 3D look, I
realized that I could not do this anymore, but I chose THREE levels of PURE
gray for the pallette (something like 3-3-3, 8-8-8, and 12-12-12) and I *still*
get black screens when importing graphics.  Even when I went to 0-0-0, 8-8-8,
and 15-15-15 for colors I sometimes get all black screens, or black on gray,
though it doesn't happen nearly as often as it did when I had "impure" grays in
the pallette.
>
> 
>Kevin Davidson, Asst. Moderator AmigaZone Vendor Support - PORTAL
>               <soft-logik@cup.portal.com>
>        SOFT-LOGIK BBS (PCP MOSLO) (314) 894-0057

By the way, I recently bought Zipperware's DTP pack, which is full of nice 
postscript fonts.  PageStream will use almost all of them, at least for display
on the screen.  Many of them will kill PageStream when printing them out to my
Deskjet, however.  In some cases the program just freezes up after printing out
about 1/4" of the page, and with some fonts it crashes the computer.  Since all
of these fonts still work just fine with Post 1.6 (and I can print them out
from PageStream using the Postscript driver) I am getting concerned about the
program's internal font rendering routines.  If just this was fixed, I would be
in *heaven*.  Really.  :-)
--------------------------------------
My operating environment:

	- 68000 (14 MHz with AdSpeed)
	- 2 Meg Agnus with 2 Megs chip RAM
	- 3.5 Megs Fast RAM
	- 40 Meg HD
	- OS 2.04 in ROM
--------------------------------------

    _____ _____ _____	   Steven Meloche
      |   ` | ' ` | '      ITT Aerospace/Communications Division
      |     |     |        San Diego, CA
    __|__   |     |        ...ucsd!dcdwest!steve