[futurebasic] Re: [FB] Which INCLUDES to use for Appearance with PG?

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : May 2002 : Group Archive : Group : All Groups

From: Joe Lewis Wilkins <PepeToo@...>
Date: Tue, 28 May 2002 09:03:11 -0700
Hi Brian,

This definitely appears to be a potential FAQ, so will you make
it a point to summarize your findings once you've got a solution
to your dilemma, and post it as a FAQ or send directly to me.

TIA,

FAQmeister Joe

Brian Stevens wrote:

> Folks----hopefully this is simple. I know this has been discussed
> before, but I can't find the post. So, please bear with me.
>
> BACKGROUND
>
> I am building a short demo to do Appearance Tabs in a PG project. I
> realize PG does not generate an "Appearance Compliant" project, so I
> just created a new one in the editor (Project==>New
> Project===>Appearance Compliant) and copied my PG-created project
> files to my newly-created Appearance Compliant project. As you know,
> PG automatically adds the header RNTM FBII.incl, so I added Rntm
> Appearance.incl to the headers in the project. In my code I have a
>
> #if ndef _appearanceRuntime
> compile shutdown "Must be compiled as an Appearance project"
> #endif
>
> just to make sure I'm compiling as an Appearance project.
>
> So my concatenation order of headers is:
>
> RNTM FBII.incl
> Rntm Appearance.incl
>
> MY PROBLEM IS
>
> When compiled I receive lots of errors about duplicate constants
>
> If I compile with only RNTM FBII.incl, my conditional compilation
> message ("must be compiled as an Appearance project") kicks in. If I
> compile with only the Rntm Appearance.incl, I'm missing many of the
> variables PG needs, so they are reported as undefined.
>
> I'm sure there is another permutation that works, I just haven't
> found it yet. Please set me straight (code-wise!)
>
> TIA......Brian