Name: boT120536 Date: 01/23/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

DragSourceContext uses an AND when it shouldn't. Search for the following code
in DragSourceContext:

protected void updateCurrentCursor(int dropOp, int targetAct, int status)
{

// if the cursor has been previously set then dont do any defaults
// processing.
if (cursorDirty && cursor != null) {
cursorDirty = false;
return;
}

and replace the if statement with:

if(cursor != null)
{
    cursorDirty = false;
    return;
}

Note the comment implies this behavior, but because this method is called
repeatedly, you can't keep cursorDirty as true, even though the cursor variable
may be non-null.

You probably don't need cursorDirty at all, since the context should use
whatever non-null cursor is set, or a default. The fact that it changed doesnt'
really matter to the update cursor method.

As a feature request, you might add both a drop and non-drop cursor (implied by
the doc) so that a special cursor can be used in either case.
(Review ID: 112327)
======================================================================