>On Wednesday, June 11, 2003, at 02:46  AM, Jay Reeve wrote:
>
>>>Hi all.  Was wondering if someone can tell me what I'm doing wrong 
>>>here. The following from an example found in the Reference eDOC of 
>>>Release 7 under the USR GETPICT function that captures the screen 
>>>and displays it in a small window.  I tried to modify it slightly 
>>>to save it to disk, and it does.  But it only saves it in black 
>>>and white even though I am running millions of colors on my 
>>>monitor and even the window it displays it in is in color.
>>>
>>>The file saving routine worked fine in FBII and saved it in color, 
>>>but not in FB^3 it seems.  I've tried to figure out how to save it 
>>>in color for about 5 days now without resorting to asking for 
>>>help, but I've now lost my stubborness and am asking if anyone can 
>>>give me a clue.;-)
>>>
>>>TIA,
>>>
>>>Darron Forehand
>>
>>Darron,
>>
>>  I'm no expert on this, but a bit of googling suggests that 
>>something in your buff% header is causing the PICT to be read as 
>>version 1 rather than version 2. You don't indicate what is in this 
>>header, nor how it's created. The adaptation below shows that your 
>>pict handle can be saved, read back, and displayed in color, but I 
>>don't know how you get that into a PICT file format. If that isn't 
>>necessary, maybe this will help.
>>
>>  e-e
>>  =J= a  y
>>   "
>
>
>Good clue. The header was correct, it was the main portion that went 
>awry because it was passing the main handle itself as the address 
>(typo , easy to make) instead of @'ing it or [ ] it.
>
>Your pointing that area out for another look made me check my own 
>PICT writer, and I saw the [ ] omission... I missed it earlier.
>
>@,[ ] , { }... Good time for your pointer and variable passing school lessons.
>
>
>Robert
>:oist

Good catch! I should have seen it, too, but I was distracted trying 
to learn about PICTs.

  e-e
  =J= a  y
   "