(OBC 2.5.1, 2 March 2005)
In both PalmSource documentation AND OBC documentation,
it is specified to use a tver resource with ID of 1000,
but OBC only compiles and uses the resource properly if
I use an ID of 1 and not 1000.
I have not enabled auto-versioning.
Logged In: YES
user_id=574706
Originator: NO
Here comes my 2 cents:
I belive one tver is enough.
If auto-versioning is checked OnBC should check the included .Rsrc:s for occurences of ResType: 'tver'.
If found, check the ID
If ID == (1 || 1000): use it for auto-versioning
If NOT found (or if other tvers is found), create a new tver 1
If auto-versioning isnt checked No action should be taken.
I'll move this to tasks, and as you Lincoln had started an investigation on the matter and thus has started to work on this I assign you as Poc.
Logged In: YES
user_id=736434
Originator: NO
This task isn't talking about auto version, it's more about how OnBoard ASM puts in a tver 1 resource when it first creates your app. It also copies any tver resources your app has but if you don't have your tver as 1 (eg. if you've used 1000), it seems to be ignored by Palm OS (at least in Launcher -> Info -> Version).
Given the handling of Palm OS itself with tver 1 vs 1000, I'm inclined to do nothing here. The docs should be updated to mention tver 1 instead of tver 1000.
A solution for this would probably need to remove both tver 1 and tver 1000 from the app (just as code resources are now removed) and then to copy in any tver from the .rsrc as tver 1000. Even then, I suspect compatibility with older versions of Palm OS may be impacted (though how important tver is, I don't know).