11-11-2010 07:32 AM
Currently there are many non definition updates which do not change the version number in NIS, N360, NAV, etc.
I think any NON definition update should always change the version number. I also think it would be useful to show a high level definition database version in Support > About. Of course there are several different types of definitions so which one to use? But could there be some sort of indicator as to the database version?
For the non definition updates it creates more confusion in the forums because the version such as 126.96.36.199 does not mean much and certainly does not indicate if the user is truly up to date. We can't just assume that live update has taken care of it and some have live update turned off anyway.
It seems it should not take much to have the version updated when there is a program or engine update, 188.8.131.52 could bump to 184.108.40.206 for example.
Thanks for your consideration.
11-11-2010 07:36 AM
By the way I know you can get the various definition versions from the live update History log, but having a "composite" database version reported right in Support > About would make it easier to know at a glance that all the definitions are up to date.
04-19-2012 03:48 AM - edited 04-19-2012 03:49 AM
A Firefox compatibility patch (for NIS or N360) does not always result in a new vsn number.
And what is really confusing:
The latest beta vsn of a product has the same vsn number as the later final product!
But many files are different between lastest beta and final version.
--- Bring back the offline vault // N360 v6.4 on german 64 bit win7, IE9 ---