You didn't read my post. I need to know the version AFTER the updater has verified and updated all files. In that case a version number should describe the current state of the installed packages.
I obviously read it, I just don't agree with you.
You said we should display a version number "after" the update. Ok, since the update and the check are the same process, and if files are updated they are not downloaded, the very fact it hasn't downloaded anything, indicates you have the LAST version, no matter what.
As an example:
- We release version 1.0. Program shows that number after checking all files, because they all checks updated.
- We release version 1.1, made by 100 new files. Updater tries to download them, and get 90 update files and 10 files from the old version.
Which version should we display in this case ?Still 1.0 ? Users would be confused because they ran the update and couldn't get the 1.1
1.1 ? Users would still see those last 10 files downloaded over and over, and would be confused because they think they have the "correct" version.
Please don't argue with me about software versioning, it's my daily job and even for your software this is doable. Literally every single software does that and it should be possible for GSX too.
I'm arguing because I don't agree with you. And most software versioning out there is flawed, because it displays a version number without being sure of it, just to provide users with a fake sense of security.
There is no factual reason not to have a version on the software. The way you're working with it is plain intransparent for everyone.
It's exactly the opposite: this way is more transparent, precisely because it indicates, file by file, if there's a problem with one of them.
A version number describes a state of a product as a whole that is shipped (e.g. with the offline installer). It should be incremented upon every release at least, best for every change. Those are basics of software development, it's not like I'm asking for rocket science.
Flawed assumption that won't provide any help if sparse files in the package are not the correct version, for any reason.
Yes, it's easy, please introduce a version number so we can see which state we are on. And increment the version number upon each update you release at the very least.
We can't do that, just to make users happy, but it won't make the program any different and they would still have exactly the same issues, if the program is getting the wrong file from the server. If would be of course MORE confusing because, you'll see conflicting information between a version number that is "correct*, with some files that might not.