JDK-6331837 : Two Swing DnD methods - rename one and remove another
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-10-03
  • Updated: 2017-05-16
  • Resolved: 2005-10-13
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.
JDK 6
6 b56Fixed
Related Reports
Relates :  
Description
Two new Swing DnD methods need revision:

TransferHandler.TransferInfo.getDropAction():
    It is unclear what this method will be used for and I believe it could pose a problem when DnD actions are dealt with in a later release. It should be removed.

TransferHandler.shouldIndicateAnyway():
    This method is currently only called to allow the developer to have the component indicate the drop location when canImport() returns false. It makes sense however for the method to also allow them to NOT show the drop location when canImport() is true. It should be renamed to shouldIndicate() and be called for every import.

The new signature should be:
    boolean shouldIndicate(TransferInfo info, canImport boolean)
The canImport boolean will represent the return value from the previous call to canImport() and by default this method should simply return that boolean (to have the drop location indicated only if canImport() is true).

Comments
EVALUATION The requested fixes are being made.
2005-10-03