JB is probably right, he's been programming these things this longer than I.
Nevertheless, from my experience I have encountered only one problem with multiple resource files. This was when I didn't give the forms Titles in MORE than one resource. The header generates duplicate defines in this case and it will not compile....I could only have one resource that contained forms without titles. I have had as many as 32 resource files (some from a shared library)using maybe 250 unique forms and alerts or so without any incident (other than the warnings mentioned earlier). I have found multiple resources make it easier to organize my larger projects. i.e. communications forms, database forms,etc.. RickG -----Original Message----- From: JB Parrett [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2000 9:49 AM To: Palm Developer Forum Subject: Re: CodeWarrior and multiple rscr files : a good idea ? on 8/25/00 5:35 AM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote: > The sample apps that come with SDK3.5 uses multiple rscr files. However, > I don't think Constructor is the one that is keeping resourceIDs unique. > I noticed that those rscr files are also not automatically generating > rscr headers. Anyone care to comment on this? > > thomas wrote: >> >> Hi folks, >> >> Has someone ever tried to put multiple rscr files (constructor >> ressources) in a project ? >> Are the warnings "ignored duplicate resources" important ? >> The reason why i'd like to use this trick is that i develop softwares >> which has a large common base and this way, i could reuse my forms >> components easily. >> any kind of advices or experiences are welcome. >> regards, >> >> thomas Generally, it is better to keep all of your resources in a single Constructor file. This way, you get a single, automatically-generated header file with all the constants you need for your code, and Constructor will normally try to ensure that you don't have conflicting resource IDs or constants (it isn't a perfect system, but it beats trying to keep it all straight yourself). My understanding is that the ROM apps were initially built using a tool that predates Constructor for the Palm - that is the reason they are in separate files. There may still be a good reason to use multiple resource files, however: source code control. Constructor uses a binary format to store its project data (resource fork on a Mac), and the merge command in some SCC systems may not work well with Constructor's data. -JB ---------------------------------------------- JB Parrett [EMAIL PROTECTED] Palm, Inc. We grow a lot faster than trees, so we miss a lot of stuff. - B. Andreas -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
