Keith, that is a very good point! there are work-arounds that problem, but the reason I was using the scheme is simply because I felt it was prefereable (to me) to
#define appVersionNumber sysMakeROMVersion(1, 0, 0, sysROMStageDevelopment, 0) and manipulate the numbers as the need prompts, rather than type "1.0000" in Constructor. that does create more coding than would be needed if I used the Constructor, since I need to convert the version number to a string, etc. the issue is definitely debatable, but is not really worth the time. what really intereseted me is the result I did not expect, i.e. the discrepancy between the Emulator and the real device. it is not improbable that I settle for using the Constructor as the "tweak" base for the version number, anyway! your point is a definite "pro" of choosing that route. thank you for the insightful input! Sincerely, sasha "Keith Rollin" <[EMAIL PROTECTED]> wrote in message news:83024@palm-dev-forum... > > At 5:02 PM -0800 4/5/02, Sasha Avanesov wrote: > >The reason I want to programmatically set the 'tver' resource is to > >ensure that if I forget to update the string in the Constructor, the > >correct one still shows up under the Info menu. I believe that it > >is a nice way to control the application version string from only > >one place in my project, the source code. > > Sasha, > > Why not do it the other way around -- have the one place where you > maintain the version number be the resource and not the source code? > The way I see it, in order for the Info dialog to show the correct > version string, the string would have to first be updated by your > application, which means that the version string is incorrect until > you run your application for the first time. > > -- Keith > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
