I just encountered a strange behavior of a custom control compiled
with .NET 1.0 and used from .NET 2.0: If the newly inherited property
BorderStyle is set to Fixed3D, the coordinates returned by MouseMove
have an offset of 2 pixels (the border thickness), i.e. (2,2) is
returned for the upper left pixel of the client area.
I think the coordinates should be relative to the client area.
Indeed, a test control created with .NET 2.0 returned (0,0) for
the upper left pixel of the client area when using Fixed3D.
Did anyone experience this before? It looks like a bug,
but of course, I might be doing something wrong.