Skip to content

Commit

Permalink
Fix typos in DragEvent.java
Browse files Browse the repository at this point in the history
  • Loading branch information
nlisker authored Sep 4, 2024
1 parent ac780bd commit 2a78027
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@
* Inside a {@code DRAG_DETECTED} event handler, if the
* {@code startDragAndDrop()} method is called on a node or scene and a dragged
* data is made available to the returned {@code Dragboard}, the object on which
* {@code startDragAndDrop()} has been called is considred a gesture source
* {@code startDragAndDrop()} has been called is considered a gesture source
* and the drag and drop gesture is started. The {@code Dragboard} has system
* clipboard functionality but is specifically used for drag and drop data
* transfer.
Expand Down Expand Up @@ -133,7 +133,7 @@
* {@code DragBoard.getTransferModes()} (set of transfer modes supported by
* the gesture source) and {@code DragEvent.getTransferMode()} (default
* transfer mode issued by platform, driven by key modifiers) can be used.
* It is poosible to pass more transfer modes into the
* It is posible to pass more transfer modes into the
* {@code acceptTransferModes(TransferMode...)} method. In this case
* it makes the decision in behalf of the
* application (it chooses the default mode if it's supported by gesture source
Expand Down Expand Up @@ -238,7 +238,7 @@ public final class DragEvent extends InputEvent {
/**
* This event occurs when drag gesture exits a node. It's the
* bubbling variant, which is delivered also to all parents of the
* eixited node (unless it was consumed). When notifications about
* exited node (unless it was consumed). When notifications about
* exiting some of node's children are not desired,
* {@code DRAG_EXITED} event handler should be used.
*
Expand Down

0 comments on commit 2a78027

Please sign in to comment.