UI: Generalize drop target API, support them for UI views #105963
|
@ -61,8 +61,13 @@ void attribute_search_add_items(StringRefNull str,
|
||||||
bool is_first);
|
bool is_first);
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Interface class to implement dropping for various kinds of UI elements. This isn't used widely
|
* This provides a common interface for UI elements that want to support dragging & dropping
|
||||||
* yet, only UI views and view items use it.
|
* entities into/onto them. With it, the element can determine if the dragged entity can be dropped
|
||||||
JulianEisel marked this conversation as resolved
Outdated
|
|||||||
|
* onto itself, provide feedback while dragging and run custom code for the dropping.
|
||||||
|
*
|
||||||
|
* Note that this is just an interface. A #wmDropBox is needed to request instances of it from a UI
|
||||||
|
* element and call its functions. Currently only #AbstractView and #AbstractViewItem have this and
|
||||||
|
* make use of the interface this way.
|
||||||
*/
|
*/
|
||||||
class DropTargetInterface {
|
class DropTargetInterface {
|
||||||
public:
|
public:
|
||||||
|
|
Loading…
Reference in New Issue
This sort of "would probably be nice to use this more in the future" comment shouldn't be added to main I think. That makes sense in code documentation or design tasks, but the code should stand for itself generally, and this comment will just become out of date otherwise.