-
-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design question #12
Comments
From [email protected] on May 06, 2010 09:23:35 I mainly used them because all of the examples I was working from used them! However, the However, judging from yourself and FreakOnALuis' issues, it looks like this is not the correct (You may also want to merge recent changes from trunk into your branch, btw) |
From [email protected] on May 06, 2010 09:24:26 |
From [email protected] on May 06, 2010 09:59:51 Firstly, I wanted to support the drag effect adorners on my whole application. To do this I Secondly, I've got a control that I need to support drag and drop which I want to put in a The only issue I have found, which I'm not sure is because of the events used, is that I've |
text box issue will be published in 0.1.3.7 |
Original author: [email protected] (May 05, 2010 09:27:51)
Hi Grokys. Looks like its getting busy on the drag and drop front!
Anyway I've been playing around on my branch of the code. One thing that
I've needed to change is the events from the 'Preview' versions to the
standard event version. i.e. Switching the events from tunnelling to
bubbling.
This change means that I can put nest controls that all support drag and
drop. (I think this is also the issue that FreakOnALuis is getting when
using a slider on a draggable element.)
So my question is what was the reason for picking the tunnelling event? So
far I haven't found any issues with making this change but just because I
haven't found anyway doesn't mean there aren't any. Am I missing something?
Thanks,
Jon
Original issue: http://code.google.com/p/gong-wpf-dragdrop/issues/detail?id=12
The text was updated successfully, but these errors were encountered: