Add a "new version available" feature.

[GoogleCodeExporter]

Ko Minn Kyaw requested a feature which checks for the latest version. Normally, 
I don't like programs popping up dialogs to inform you of this, so maybe we can 
do it like this:

1) Put a file in SVN (that way we have a "permanent" location). This file 
contains the current version number (e.g., 1.8). 
2) When WaitZar starts, pull the file and check if the current version is 
newer. If so, add an item to the context menu reading "New version available.". 
Have this link to the download page. 
3) Disable this if the user's using a nightly (preview) version, or if they're 
using the "stand-alone" WaitZar (with no config files & minimal features.)
4) Don't do anything if there's no internet connection.
5) Add a second option to the SVN file which works like this: "ignore-1.7". 
That means, if you're using 1.7 and you detect a new version, don't add the 
"Upgrade" link. This is needed because, if there's an error in the upgrade 
code, it'll only be noticed when the next version comes out. So we need a way 
to avoid crashing "old" releases.

This should be fairly easy. I think I can put this into the next release, and 
have it be fully tested by 2.0.

Original issue reported on code.google.com by seth.h...@gmail.com on 17 Jun 2010 at 9:56

• Blocking: #89

[GoogleCodeExporter]

I've modified the context menu extensively; now, adding a new item doesn't 
immediately skew the other items. 

Original comment by seth.h...@gmail.com on 18 Aug 2010 at 7:13

• Changed state: InProgress

[GoogleCodeExporter]

Added. Too bad no-one will see it until 1.9. 

This causes a balloon to appear after the "Welcome to WZ" balloon; clicking on 
said balloon will launch the WaitZar web page.

Shame on you, Microsoft, for such terrible "ShellExecute()" documentation. It's 
the first place I looked, and it didn't even say that this was the right way to 
launch a web page.

Original comment by seth.h...@gmail.com on 15 Sep 2010 at 12:19

• Changed state: Fixed

[GoogleCodeExporter]

Re-opening.

It just occurred to me: our approach to nightly upgrades (just ignore them) 
isn't TECHNICALLY correct.

For example, we know that 1.8 > 1.7NIGHTLY.

So, we'll check the VERSION (not FULL VERSION) against the list.

That way, 1.7NIGHTLY still matches against 1.7, so we know that, when 1.8 comes 
out, 1.7 AND 1.7NIGHTLY will be obsolete.

Original comment by seth.h...@gmail.com on 15 Sep 2010 at 12:23

• Changed state: InProgress

[GoogleCodeExporter]

Fixed.

Original comment by seth.h...@gmail.com on 15 Sep 2010 at 12:28

• Changed state: Fixed