>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. 

Brian,

What you are trying to do may not be impossible, but it certainly isn't 
simple. PG requires a long list of runtime FNs to keep all its globals up 
to date. It does not know how to do appearance things. Appearance knows 
nothing of all those globals and special PG conventions. They are 
completely different animals, and cannot cross breed.

That said, you can use appearance items within PG as long as you do all 
the toolbox writing to create and manage them as user items. Alain used 
to have an incl you could use to help do this. I'm not sure it was 
complete enough to do tabs, but maybe.

There may be things you need to do with your appearance/user items for 
which you can borrow or adapt code from the Appearance runtime, but it 
will take a lot of work to identify it and modify it to work with PG. It 
can certainly be done, but probably requires a pretty sophisticated 
understanding of both PG and Appearance.

Sorry for the bad news--maybe someone else can be more encouraging, but I 
doubt it. Eventually, I think Staz may incorporate PG-style capabilities 
in an Appearance-compliant runtime, but it won't be this month (year?).

 e-e
 =J= a  y