🚀 go-pugleaf

Well, that would seem to be the predicament.  I would prefer not to require
use of the shift/alt/ctrl keys or even the use of a right mouse key, yet
something has to distinguish the intent of the action.  Currently the
gesturerecognizer is initialized with DnDConstants.ACTION_MOVE but my code
actually performs as a copy.  If I set things to recognize another action,
I'll still have to get the decision from the user as to which one to use.
It would prevent the overhead of having to toggle the listeners, though it
would mean that the JPanel has to be a drop target and the buttons
themselves would have to be transferable - all that just to reposition the
component on the screen.

Nobody rides for free.

Any other options spring to mind?

-J

"John P. McGrath" wrote:

>
> I am beginning to understand.  The problem is that the same gesture (in
> DnD terminology) is initiating both the move button code and the drag-
> and-drop transfer of the transferrable object.  What gesture are you
> trying to use for each operation?
>
> --
> John P. McGrath
> <JPMcGrath@fast.net>
> <jpm@nscs.fast.net>