This API is too limited in my opinion. In general, one needs at least a coordinate relative to the window and to receive updates when this coordinate changes. In my tests on X11, the app does not receive usual cursor or touch events when a file is hovered, hence the window has no way of determining the current coordinate.
Suggestion: add a "source" parameter to DroppedFile, HoveredFile, and HoveredFileCancelled, and continue to deliver cursor and touch events as normal.
Alternatively, include a coordinate and add a HoveredFileMoved event.
(I have not investigated platform capabilities and don't have a direct use, but wish to add support to KAS, which must determine the widget under the drop.)
This API is too limited in my opinion. In general, one needs at least a coordinate relative to the window and to receive updates when this coordinate changes. In my tests on X11, the app does not receive usual cursor or touch events when a file is hovered, hence the window has no way of determining the current coordinate.
Suggestion: add a "source" parameter to
DroppedFile,HoveredFile, andHoveredFileCancelled, and continue to deliver cursor and touch events as normal.Alternatively, include a coordinate and add a
HoveredFileMovedevent.(I have not investigated platform capabilities and don't have a direct use, but wish to add support to KAS, which must determine the widget under the drop.)