There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.
There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.
There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.
H.P.Dubey
There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.
H.P.Dubey
There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.
H.P.Dubey
There is no mechanism in D+D to identify the source of the dragged object. Very much by design, it can come from an entirely different process that’s completely out of reach. If you need any additional info beyond what’s in the object that’s being dragged then you’ll need to add that to the object. Not at all an issue as long as the D+D is inside one app, you can create a little helper class to store whatever you need.