jpeters

The project explorer window doesn't use a diagram to implement its behavior. It is a VI front panel that has some hooks (written in C) to customize behavior of the controls. This uses an event mechanism that more closely matches what a built in control uses rather than using an event structure. That said, I think it would be great if it were possible to write the project window in 100% G :- at least the drag drop behavior anyway. About the "Drag" event, I assume that you actually mean the "Drop" event or one of the other target side events. I have had several suggestions stating the same thing. This actually would be more like the old type drag events for the tree. The problem is, that Drop events are defined at the control level, and Drag Between doesn't really make sense for something like a string control or graph. This doesn't necessarily mean that we couldn't make a special drop event for the tree control -- but overriding events to include specific data for a control is not something we have done generally. At some point in the near future, I am going to write a post about how drag and drop can be improved on the LabVIEW Developer Feature Brainstorming board. Please (both of you) feel free to register your feedback over there if you get a chance. (I will post here when I have actually created the topic as only us internal guys are allowed to do so). Thanks Jeff P

I assume that you mean that the little drag bar disappears and that items aren't inserted on drop. This is (unfortunately) expected behavior. If you register for Drag Over, Drop, or really any of the other drag and drop events on a target then the default behavior provided by LabVIEW is never executed. I struggled with this quite a bit when I was implementing Drag and Drop as a feature in LabVIEW 8.0.... The problem is, that if you accept some datatype that the tree/listbox/string/ whatever doesn't know about, it won't know how to draw the feedback. Also, on the Drop event specifically, there is not a way currently for LabVIEW to know if you handled the event (by inserting the item) or if LabVIEW should do the insertion. Similar issues can arise if you draw your own feedback for drag drop. Therefore, the rule (for now) is that if you register for any drop target event (Drag Over, Drag Enter, or Drop) that you must implement all the drag and drop behavior yourself. I welcome any feedback on this. This is actually a big interest of mine to revisit the drag drop events and restore some default behavior when possible or at least provide an intuitive way to mimic default behavior. Jeff P LabVIEW R & D