Inserting a DropTargetInfo into a UI element allows you to specify the necessary properties for a drag-and-drop operation. You can also insert a DropOnRowTargetInfo into a Table, which allows you to specify at row level whether a drop target is valid.
This determines whether this DragTargetInfo is enabled; if set to false, the user cannot drop an object here.
This property allows to indirectly reference a DropTargetInfo by name. In such cases, you can aggregate multiple DropTargetInfos and their names need to be unique only within that aggregation. Some UI element property of the parent is used in connection with data binding to individually select the applicable DropTargetInfo, - for example for each table row.
This defines whether the drag-and-drop operation is restricted to the local Web Dynpro component instance. Possible values are:
This determines whether this DropTargetInfo supports a drag-and-drop operation using the secondary mouse button. This results in a context menu being requested, an onDrop event is not triggered.
A space-separated list of identifiers that is used to determine compatibility of a given drag source with potential drop targets. We recommend specifying the tags according to these rules:
ID part | allowed characters |
---|---|
Namespace |
A to Z |
|
a to z |
|
digits from 0 to 9 |
|
hyphen - |
ID |
A to Z |
|
a to z |
|
digits from 0 to 9 |
|
hyphen - |
|
period . |
Examples:
Name |
Interface |
Type |
Initial Value |
Bindable |
enabled |
IWDDropTargetInfo |
boolean |
true |
bindable |
name |
IWDDropTargetInfo |
String |
|
not bindable |
scope |
IWDDropTargetInfo |
WDDragDropScope |
componentInstance |
not bindable |
supportSecondaryMouseButton |
IWDDropTargetInfo |
boolean |
false |
not bindable |
tags |
IWDDropTargetInfo |
String |
|
not bindable |
Javadocs on IWDDropTargetInfo: http://help.sap.com/javadocs .