Check For Updates

[ChrisGreaves]

I read through the four topics delivered by this search
Every member is unique and so every member has needs which may differ from other members.
We do not want void working 24/7 updating updating notices.

I happen to be running "Version 1.5.0.1341a (x64)" and I'd be happy always having the very latest available-for-download version on my system.
(1) Happy to be on the bleeding (grin) edge of technology
(2) Important to me: My screen shots display the version in use at the time I tapped PrtScr, so my images would be version-stamped.
(3) Glutton for punishment (grin)

I happen to dislike applications that tell me every time I load them that "a newer version is available", forcing an extra mouse or hand-movement to dismiss the notice so that I can get on with my job.

If I were running in a production environment I might want to restrict my versions to the latest public (non-alpha) release, which today appears to be "Everything 1.4.1.1022".
That given, if an update to 1.4 came out I would like to know about it; but I would NOT like to know about updates to 1.5

Each one of us can dream up a similar set of conditions.

I am starting to think of a multi-value switch that constrains update notices to:-
Never inform me; I am a Big Boy now and can go look for myself, or will be told in response to a problem post.
Inform me only of changes in my chosen version range to the first partition number (be it 1.3 or 1.4 or 1.5 etc)
Inform me only of changes in my chosen version range to the second partition number (be it 1.3,7 or 1.4.5 or 1.5.1 etc)
Inform me only of changes in my chosen version range to the third partition number (be it 1.3.7.4 or 1.4.5.3 or 1.5.0.1342 etc)
When you inform me, inform me only once and then please leave me alone. This might require storing "latest update version notice" in the INI file to show that it need NOT be re-issued.

I think that as long as the user has some control (perhaps like the flexibility proposed above), then once a version is published, "it is out there" and is up for grabs. In that sense if version 1.5.0.1355a proves to be toxic, the best answer for us all might be for Void to withdraw that version until the toxic problem is fixed, then re-issue it as the next version 1.5.0.1356a - but Void would have better ideas about that.

I think that if an update describes a change, then that description should be included wherever it can be. "Now you see it now you don't" can only confuse someone whose work depends on that area or feature.

This seems to be very complex, but I think that it really very simple in terms of how updates are announced through the "Check For updates" settings:-
(a) I don't want to know.
(b) I want to be informed only of changes within by chosen platform (alpha, beta, or public)
(c) I want to be informed only to a specific level of detail (partition number)
(d) I need to be told only once OR I enjoy being nagged.

Cheers, Chris
P.S. What would be really Cool would be the Help, Check for Updates popup to include the current version number in the chosen version range (in my case the 1.50.1342a, in someone else's case the 1.4), and in this box and the Help About box include a link to the forum post that announces and discusses the latest roll-out. C

[void]

There's a beta update channel ini setting for Everything 1.4.

The Everything 1.5 alpha will always use an alpha update channel.
I'll post out Everything 1.5 alpha update notifications once there's a more stable release.

I will consider selecting an update channel in Help -> Check for Updates.
I will consider showing a link to Everything 1.5 under Help -> Website and Help -> About
Thank you for the suggestion.

[ChrisGreaves]

There's a beta update channel ini setting for Everything 1.4.

The Everything 1.5 alpha will always use an alpha update channel.
I'll post out Everything 1.5 alpha update notifications once there's a more stable release.

I will consider selecting an update channel in Help -> Check for Updates.
I will consider showing a link to Everything 1.5 under Help -> Website and Help -> About
Thank you for the suggestion.

Thanks, Void!
Chris