Lol ;) I actually thought about that myself when i fixed that bug (that did never "happen", but still). This is a "hello world" sized app that was coded in an evening and still I manage to get bugs in it, and then I've been working as a professional developer for 15 years ;) Think about writing a friggin flight simulator that has to run on all weird rigs in the world and a crazy state combination to keep track of... :)

But very soon I will get a new version ready - it's in internal testing right now but we found a bug that I'm not allowed to speak about that may take a few days to fix ;) To make you happy I have this for you all to view in the meantime!

Picture of russian village that will appear in ClodWatcher version 2.0:
http://academic.umf.maine.edu/scotte...acd/farm_1.jpg

We are working at the alignment of the fences so no whining about that please!

The horse is the wrong colour :(

heheehe

Humour!!! :D

Thanks Mazex, works as advertised :grin:

I get a CTD when pressing the [X] button in the top right. What's up?! :confused:

:-P

He he, even though you did joke - you actually touched something that is kind of a bug (or more of an aesthetic glitch) in the current version. If user has started the background thread that polls the server and then press the "real" exit button down in the right corner without stopping the watcher it will notice that and nicely terminate the poll thread before closing the main form. BUT - If you press the x I did not handle the event there (FormClosing) so that it should check if the user has pressed the x without stopping the background thread :) A good application is supposed to anticipate that the user maybe not does things as they are supposed to and I have changed the code for version 1.0.4 to include checking that event too... But I will not do a new build of it until something else appears...

This is the tough world of being a developer... Thinking of all the things users can do that they are not supposed to do. Having the "watcher" thread running when closing the form with the x will not cause any errors though and the "watcher" thread will die as it is defined as a background thread when it gets orphaned, but it's not elegant ;)

Okay so when can we expect a patch?
:)

I think we need an application to do regular checks for Mazex's patch being posted... :rolleyes:

I'd write one, but I think it would probably need beta-testing first. Any volunteers? :grin:

I don't think he claimed it's a crystal ball.

Oh, wait, thats a different thread.