Path: utzoo!attcan!uunet!pdn!boake2!jc3b21!fgd3
From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice C Power Windows
Message-ID: <806@jc3b21.UUCP>
Date: 3 Dec 89 16:16:28 GMT
References: <[2577758d:2917]comp.sys.amiga@tronsbox.UUCP>
Organization: St. Petersburg Jr. College, FL
Lines: 39

From article <[2577758d:2917]comp.sys.amiga@tronsbox.UUCP>, by tron1@tronsbox.UUCP (HIM):
> Listen , I am using Power_Windows 2.5 , and Lattice C 5.04 .
> 
> The problem is in custom images for gadgets. I used PW2.5 to set up the
> gadgets using DpaintII brushes, and In power windows it looked GREAT.
> 
> I generated the source with ALL flags on (including BORDER and LOCAL
> STRUCTURES) , and with all off with the same result.
> 
> When the Code generated is compiled into the sampole program they give you ,
> the gadget images are hopelessly munged. The gadgets ARE there , and If I do
> this without the custom imagrey , it works right.
> 
> ANyone used this combo and can tell me what the problem is?

     Power Windows doesn't put the chip keyword in its source.  The
simplest fix is to revise the source generated by Power Windows by adding
"chip" to your image definitions.  For example, Power Windows might
generate:

     USHORT RightArrowImageData[] =
     { ... };

You need to change it to:

     USHORT chip RightArrowImageData[] =
     { ... };

That tells the Lattice compiler to store the image data in chip RAM.  If
you have the Manx compiler you can't use the chip keyword.  With both Manx
and Lattice you can compile the module containing image data separately
with a compiler flag specifying chip RAM.  

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...uunet!pdn!jc3b21!fgd3