JDK-4151246 : Solaris: MMouseDragRecognizer doesn't work properly
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.2.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.5.1,solaris_2.6
  • CPU: generic
  • Submitted: 1998-06-22
  • Updated: 1999-01-19
  • Resolved: 1999-01-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.2.0 1.2fcsFixed
Related Reports
Duplicate :  
Relates :  
Description
On solaris, drag gesture recognition doesn't work using new beta4 API DragSource.createDefaultDragRecognizer(). Further investigation shows that  MMouseDragRecognizer is broken, which prevents createDefaultDragRecognizer() from working.

The problem is found on jdk1.2beta4 J build on Solaris. 
To reproduce the problem, please see: /home/tinasu/ws/Drag-n-Drop/SmallTests/TestButton.
BTW,The same test works fine on Windows.
 

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2fcs INTEGRATED IN: 1.2fcs VERIFIED IN: 1.2fcs
14-06-2004

EVALUATION Agreed, was was because of poor logic in MMouseDragGestureRecognizer.java larry.cable@Eng 1998-06-22 There stills seems to be problems though with the X Event retention in AWTEvents. larry.cable@Eng 1998-09-03 I am re-assigning this bug to AWT. The problem is that XEvents are still being discarded from their AWTEvents too soon. This results in DnD operations failing to start due to the missing X Event which is required by Motif to initiate the drag. larry.cable@Eng 1998-09-03 --------------------------------------------------------------------------- jeff.dunn@Eng 1998-09-15 I need 2 things: 1. A reproducible test case. The test case in the Description does not exist (/home/tinasu/ws/Drag-n-Drop/SmallTests/TestButton) 2. A description of the failure (a crash? incorrect data? the operation is ignored?) I am marking this bug incomplete, because I can't reproduce it with the information included here. ------------------------------------------------------------------ tina.su@Eng 1998-09-16 : MMouseDragRecognizer doesn't work on solaris, causing the core dump from using dnd API DragSource.createDefaultDragGestureRecognizer() when a drag operation is initiated. The test case in: /home/tinasu/ws/Drag-n-Drop/SmallTests/Bug4151246 will demonstrate the problem. You can also replace DragSource.createDefaultDragGestureRecognizer() with a workaround "new MyDragGestureRecognizer()" to see a correct dnd behaviour. Please let me know if you need more info. Here is the stact trace: starting Drag Exception occurred during event dispatching: java.awt.dnd.InvalidDnDOperationException: The operation requested cannot be performed by the DnD system since it is not in the appropriate state at sun.awt.motif.MDragSourceContextPeer.startDrag(Compiled Code) at java.awt.dnd.DragSource.startDrag(Compiled Code) at java.awt.dnd.DragSource.startDrag(Compiled Code) at java.awt.dnd.DragGestureEvent.startDrag(Compiled Code) at DnDSource.dragGestureRecognized(Compiled Code) at java.awt.dnd.DragGestureRecognizer.fireDragGestureRecognized(Compiled Code) at sun.awt.motif.MMouseDragGestureRecognizer.mouseDragged(Compiled Code) at java.awt.Component.processMouseMotionEvent(Compiled Code) at java.awt.Component.processEvent(Compiled Code) at java.awt.TextComponent.processEvent(Compiled Code) at java.awt.TextField.processEvent(Compiled Code) at java.awt.Component.dispatchEventImpl(Compiled Code) at java.awt.Component.dispatchEvent(Compiled Code) at java.awt.EventQueue.dispatchEvent(Compiled Code) at java.awt.EventDispatchThread.run(Compiled Code) I am moving this into the integrated state as Jeff did the putback for this bug last night. lara.bunni@Eng 1998-09-23 tina.su@Eng 1998-09-28 - The bug fix is verified in JDK1.2 FCS-L build.
23-09-1998