Conference bulova::decw_jan-89_to_nov-90

    I'm running 5.1 and have put in a hack to allow me to print screen
    without crashing (see note 1800.*).  I don't know about 5.3, but it
    sounds like maybe the print screen feature has been altered so that you
    don't crash the system.  THIS IS ONLY A GUESS as I am not associated
    with the support group.  Anybody know if print screen works correctly
    in 5.3?
    
    Steve

I'm running v5.3-1 and have the same problem as discussed in .0.
I also had the problem with v5.3.
Note: It seems to happen to me ONLY when I try to do a print screen 'one after
the other'. Once the problem arises I can only fix it my restarting my session
(not the sever).
===Steve

>Note: It seems to happen to me ONLY when I try to do a print screen 'one after
>the other'.

I agree with you Steve, I have the same problem with VMS 5.3. It happens
if I try to do print screens one after the other.

Does anybody know something about a workaround or fixed in next version
or .....?

regards
Hansjoerg

My problem is a little bit different, but I think it suits the subject - 
PrintScreen problem......

I am running VMS V5.3 and DECWindow V2. None of the Print Screen options work 
for me because the color setup on my windows. My window background is blue and 
foreground is yellow, and whenever I captured/printed portion/entire screen, it 
captured/printed nothing except some window border. I know if I change the 
colors of my window, logout my workstation, login again, see how it works, 
repeat the process several times, I should finally get the PrintScreen to work
for me, but it used to work for my color setup in DECWindow V1 !! How come it 
doesn't work anymore?

Is there any way I can prevent tuning my color setup in order to capture text 
on the screen? Is this a bug for V2?

Any input is appreciated!!

Anne

  I assume that you are getting monochrome print screens.  When converting
color to monochrome you first have to calculate the luminosity of the RGB
triplet of the color.  When this is done, the value is then checked against
a threshold value to determine whether or not the color is ON or OFF.

  Grey-scale and dithered routines give much better results but are not
readily availble.  The color-to-monochrome method is fast and usually gives
good results.

  I wrote a print screen program that generates SIXEL files to be printed.
You have the option of either color or monochrome output.  If you select
monochrome and your hardcopy has the effect you mentioned then my program
gives you the capability to modify the threshold value so that you can get
better results.  There is a /VAL= qualifier that does this.

  There is a note in the DW_EXAMPLES conference about my program.  It is
written in Ada and I have source and an executable available in

	GSRC::DUA2:[WEST.WORLD]

  Try this out.

						-=> Jim <=-

>   I assume that you are getting monochrome print screens.  When converting
> color to monochrome you first have to calculate the luminosity of the RGB
> triplet of the color.  When this is done, the value is then checked against
> a threshold value to determine whether or not the color is ON or OFF.

Yes, in my Customize Print Screen option, I select PostScript, Black and White,
1 to 1, and Negative Image. Where can I find the information to calculate the 
luminosity of the RGB triplet of the color? And how shall I do with it?


>   I wrote a print screen program that generates SIXEL files to be printed.
> You have the option of either color or monochrome output.  If you select
> monochrome and your hardcopy has the effect you mentioned then my program
> gives you the capability to modify the threshold value so that you can get
> better results.  There is a /VAL= qualifier that does this.
> 
>   There is a note in the DW_EXAMPLES conference about my program.  It is
> written in Ada and I have source and an executable available in
> 
> 	GSRC::DUA2:[WEST.WORLD]

I did try this out, and it works fine without having to specify the /VAL 
qualifier! Thank you, Jim. But I did encounter a problem with /FULL qualifier, 
(a vertical line appears when I printed the SCREEN.SIX) I will ask the 
question in DW_EXAMPLES conference notesfile.


Anne

RE:                       <<< Note 2635.7 by CIM1NI::CHU >>>
                        -< Jim's PRINT_SCREEN works for me! >-


>>I did try this out, and it works fine without having to specify the /VAL 
>>qualifier! Thank you, Jim. But I did encounter a problem with /FULL qualifier, 
>>(a vertical line appears when I printed the SCREEN.SIX) I will ask the 
>>question in DW_EXAMPLES conference notesfile.

  About the vertical line...I think this may have to do with the printer.  If
you type out the file to a terminal (that knows SIXEL) you will not see this
line.  I have seen this line occasionally.  In fact, I have taken the same
file and printed it on an LPS40 and two different LN03's.  One of the LN03's
consistantly put this line there...by the way, this line appears just about
in the middle of the page.  The other two printers work just fine...hmmmm

  Would anyone out there have a clue as to why this is happening?  Could it
be the SIXEL introducer that I use?

  <ESC>[7 J
  <ESC>P9;;5q



  About the luminosity value...It is calculated as follows.

  l = (R * 0.299) + (G * 0.587) + (B * 114)

  The threshold value is calculated by multiplying the max color value (usually
65535) by an intensity value (0.0 .. 1.0).  The default value I use 0.51 for
this.  So if l is less than calculated threshold the color is off and if it
is greater than or equal to calculated threshold then the color is on...or in
the case of image reversal the above logic is reversed.

						-=> Jim <=-

>>.0
>>	I'm running DECwindows 2.0 on a VAXstation 2000 with VMS 5.3
>>
>>	When I do several printscreen, sometimes I get a lot of
>>DECW$PRINTSCREEN.TMP in my SYS$LOGIN directory and nothing is send to the
>>printer. The printscreen option doesn't seam to work anymore.
>>
>>	Is it a known bug or something is not set up correctly ?

Has anyone a solution to this? 

(I'm not interested in internal workarounds!, (for the time being,anyway) )