On Feb 4, 2008, at 3:29 PM, Sarah Reichelt wrote:
I've now been using this update architecture for a little over a year
now. Over that year I've seen a number of users write in thinking
that
they weren't running the latest update because the File Info dialog
for the executable said 1.x instead of 1.x.x (The about box does
report the proper version though).
Trevor, I use a similar sort of thing and almost never update the
actual application, just the sub-stacks. I store the app's version in
one of the sub-stacks, so I can update it that way. That doesn't
affect the File Info but you could do that yourself by editing the
plist file when you update.
Yeah, I currently store the actual version in the "application" stack
(stack with all my app configuration information) so that is why the
about box is always up to date.
Updating the plist file would probably work well on Mac. I hadn't
thought about that but will give it a go. The only drawback that
springs to mind is that modification date either a) won't get updated
or b) won't reflect the date you created the update. This is probably
of little consequence in the majority of cases though.
For windows this might be a little trickier. Perhaps a binary update
can be performed to change the version number but that depends on how
easy it is to find the info in the executable file. You may have to
resort to a system API call though. Anyone tried this with a Rev exe
created with 2.7 or greater?
Regards,
--
Trevor DeVore
Blue Mango Learning Systems
www.bluemangolearning.com - www.screensteps.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
