Duplicate :
|
|
Duplicate :
|
|
Duplicate :
|
Name: jl125535 Date: 01/27/2003 FULL PRODUCT VERSION : java version "1.4.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode) FULL OPERATING SYSTEM VERSION : Microsoft Windows 2000 [Version 5.00.2195] A DESCRIPTION OF THE PROBLEM : The current Drag and Drop specification requires that the data for a drag operation be produced locally before the drag operation. For dynamically produced data (e.g., dragging a server-based file), the data is not available and would be prohibitively expensive to create locally. The desired behavior is a slightly modified drag and drop protocol. The first change would be to let the DragSource provide only the DataFlavor objects that can be produced for this drag operation. The second change would be to add a generic callback function to identify to the application that the drop operation has succeeded and that the promised DataFlavor must now be produced. This limitation is critical to anyone needing deferred data callbacks in a native application trying to port to JAVA. An example of a potential drag and drop scenario can be found under the SWT, at http://www.eclipse.org/documentation/html/plugins/org.eclips e.platform.doc.isv/doc/reference/api/org/eclipse/swt/dnd/Dra gSourceListener.html. STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : 1. Try to produce a drag operation without the data in existence 2. 3. This bug can be reproduced always. (Review ID: 153350) ======================================================================
|