> I wrote: > The way this works is the system looks for requested resources (forms > and whatnot) in the most-recently-opened-database first, then in > other databases by order of opening.
This implies opening of the database you wish to get resources from. I apologize for any confusion. > LionScribe wrote: > > You also have to have the library open up it's own database on it's first > > time starting, and closing DB on exit. For Shared Libraries, you are correct. I am far too used to developing GLib libraries (which are opened and closed automatically at program start and exit). > James wrote: > However, just hoping that you don't collide with the application's resources > seems like a really bad idea. Oh, I never said to hope! I would expect anyone writing a library to be very, very careful when assigning resource IDs. A would be safest, as well as the slowest. B is almost insane. As long as the IDs are known, and an application is written with these IDs in mind, leaving the library database open during an application's run-life should be fine. -- Matthew (Darkstorm) Bevan [EMAIL PROTECTED] Margin Software, NECTI. http://www.marginsoftware.com Re-inventing the wheel, every time. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
