B
Bob
I completely disagree with MS's decision to make you buy a whole new version
of their product to get a fix to such a basic, glaring, long-standing bug. I
deployed an entire ERP system written in DotNet in 2003, and having
MouseLeave stop firing makes all the mouse-tracking controls in its UI look
absolutely stupid, unprofessional. There is no workaround. Now they're
telling me they're never going to fix it, that I have to buy Whidbey. It's
not acceptable. Not at all.
http://lab.msdn.microsoft.com/produ...edbackid=e4b2cafa-1f54-4216-8bc2-0ad03cc4add0
Bob
of their product to get a fix to such a basic, glaring, long-standing bug. I
deployed an entire ERP system written in DotNet in 2003, and having
MouseLeave stop firing makes all the mouse-tracking controls in its UI look
absolutely stupid, unprofessional. There is no workaround. Now they're
telling me they're never going to fix it, that I have to buy Whidbey. It's
not acceptable. Not at all.
http://lab.msdn.microsoft.com/produ...edbackid=e4b2cafa-1f54-4216-8bc2-0ad03cc4add0
Bob