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
When using two databound controls, with editable controls, if you drag an item from one to the other, a shallow copy is made, such that edits to one change the other. While many are opposed to ICloneable for not being strict enough, it is better than nothing and part of .NET.
I added ICloneable support in matelich@564f258 but didn't expand it with a sample, so I haven't submitted a pull request.
Obviously I could fix it with my own drop handler, but it seems like the proper behavior for the default drop handler to me.
The text was updated successfully, but these errors were encountered:
When using two databound controls, with editable controls, if you drag an item from one to the other, a shallow copy is made, such that edits to one change the other. While many are opposed to ICloneable for not being strict enough, it is better than nothing and part of .NET.
I added ICloneable support in matelich@564f258 but didn't expand it with a sample, so I haven't submitted a pull request.
Obviously I could fix it with my own drop handler, but it seems like the proper behavior for the default drop handler to me.
The text was updated successfully, but these errors were encountered: