You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want to implement #617 we should give the user a "notice period". Therefore the suggestion would be to mark all overloads of Click and DoubleClick which are not using directly the MouseEventArgs as obsolete.
The text was updated successfully, but these errors were encountered:
I am inclined to NOT add the Obsolete attribute and simply remove the methods for v2. Most wont notice it during upgrade because they will simply be able to recompile and it will work because they do not use any the parameters in the methods. But ill leave this issue here so we can make a final decision later.
Okay sorry that is on my :) I misunderstood this a bit.
Of course it would only make sense to mark methods a priori v2 so that the users have a chance of noticing and reacting.
But to be fair the change is very very small without any side effects. I guess one sentence in the „How to migrate“ should cover that issue.
Therefore let’s close that issue and I’ll the requirement of adding some documentation to the other one.
This is a pre-cursor for #617
If we want to implement #617 we should give the user a "notice period". Therefore the suggestion would be to mark all overloads of
Click
andDoubleClick
which are not using directly theMouseEventArgs
as obsolete.The text was updated successfully, but these errors were encountered: