|
Quick Lists
|
|
Bug ID:
|
6379813
|
|
Votes
|
0
|
|
Synopsis
|
TransferHandler should allow the developer to choose the drop action
|
|
Category
|
java:classes_swing
|
|
Reported Against
|
|
|
Release Fixed
|
mustang(b74)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4869264
|
|
Submit Date
|
01-FEB-2006
|
|
Description
|
In canImport() and importData(), the developer can query the drop action on the TransferInfo. However, they need to also be able to query the source actions and pick a different one.
Posted Date : 2006-02-01 18:51:09.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Agreed. I filed this.
Posted Date : 2006-02-01 18:51:53.0
This support has been added as follows:
TransferHandler.TransferInfo, which previously only provided information on the transfer, has been renamed to TransferHandler.TransferSupport and has been given behavior and more methods. New informational methods are:
getSourceDropActions() - returns the actions supported by the source of the transfer
getUserDropAction() - returns the action chosen by the user with their gesture
The developer can query these actions in canImport() and choose an action different from the user action by calling setDropAction() on the TransferSupport.
When a drop occurs, the final chosen action can be queried with the getDropAction() method.
As part of this fix, and additional change has been made to TransferHandler. To save the developer from having to override another method, the method shouldIndicate() has been removed from TransferHandler and moved into TransferSupport, with the name setShowDropLocation, to be called from canImport().
Posted Date : 2006-02-09 16:35:41.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |