quote:
Again, many stuff you listed, DragonQ, are not bugs at all, and even maybe some stuff didn't happened at all (refering to the so many random bugs which you all experienced but no other tester did; so either all those didn't happen at all, where misinterpreted or you are a hell of a beta tester. Personally I highly doubt you got all those 'bugs' with just quickly going thru the program, as you've said... sorry)
Quickly going through it? This was over at least a month's worth of use...and also, they did all happen, you'll have to trust me on that. I'd give more info on my system if I could be bothered, but I don't think anything in particular would cause a large number of these bugs to happen specifically on our machines.
quote:
Or this means your contact doesn't have handwriting capebilities (in this case WLM is acting in the proper way), or it means your Ink drivers aren't installed properly or another program is interfearing with it (in this case WLM can't do anything about it, it isn't an OS).
Ink drivers? All we have done is install the program. And the fact that it works sometimes and not other times is peculiar in itself. The main problem here with WLM is that THERE IS NO ERROR MESSAGE, so we have no idea what's going on - it just appears to ignore handwriting requests for no reason.
quote:
eg: 9) It is called WINDOWS LIVE! Messenger. Worst. Name. Ever.
Not only is this just a personal preference, it is also called "Windows Live" for a perfect valid reason, which is explained already many times in other threads, and explained in extreme detail on MS' own pages.
Yes, it is a personal reference. Sorry, this whole "Live" thing just shows MS has more time on their hands than they should...
quote:
eg: 25) WLM sometimes just doesn’t change your status when you’re idle after the 5 minute timeout has elapsed.
This isn't a bug at all and only depends on the status of your computer. It are other processes, processes which you even don't know about, which dictate if a computer is in idle status or not (it can even be a wake-up-on-lan bios setting). If Messenger doesn't get this idle state, it doesn't go to idle.
I guess so.
