>> When I generate my own window in a PG:PRO project I get an error that says
>> PG can't get the control list in its pG3c resource.  How can I prevent PG
>> pro from looking for the control list when I open up a Non PG window?
>> Barrie 
>> 
> 
> PG runtime is looking for its resources such as pG3c. When you build
> a window without using PG, (i.e. without using pGbuild(_yourwindow)),
> these window resources don't exist (so, of course, pg doesn't find
> them). Working with PG is, to a greater degree, an all or nothing
> proposition. :-)
> 
> Creating the window with PG should solve the problem. However, I
> assume you are creating a non-PG window for a reason. There are some
> PG functions that can be helpful for resizing of windows that
> sometimes are overlooked and there are other tricky things that can
> be done. My projects have been converted to non-PG but I remember the
> pains.
> 
> Brian
> 
> --
> To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>
> 
Brian
Thank you for your insight. I wanted to generate my own windows to
accommodate an unknown quantity of pages. (one page per window). However, I
anticipated that I would be in for a difficult time so I am creating a bunch
of spare windows in PG:PRO and limiting the number of pages to a known
quantity.
Barrie