pavel.safrata at oracle.com
Fri Apr 27 08:46:56 PDT 2012
On 27.4.2012 17:35, Alexander Kouznetsov wrote:
> Hi Pavel,
> Incompatible changes are something we should try to avoid. I've heard
> many complaints on the fact JavaFX is changing incompatibly too often.
I agree, the question is if anybody is interested in the click that is
only a first part of a double click, if getting two click events for a
double click is useful for something.
> Could you please list all the differences between listening to
> mouseReleased and mouseClicked events?
Currently the only difference is that the MouseReleased event is
delivered always to the node that was pressed, regardless of where the
mouse has traveled, whereas the MouseClicked event is delivered only to
the node that was both pressed and released.
> Best regards,
> Alexander Kouznetsov
> On 27.04.2012 19:17, Pavel Safrata wrote:
>> currently we deliver MOUSE_CLICKED event any time a node was pressed
>> and released by mouse; if the next press happens fast enough and near
>> enough, we increase the clickCount number for the events. There are
>> requests to make a standalone single-click distinguishable from a
>> first click of a double-click (and so on).
>> After some discussion we concluded that the cleanest approach would
>> be somewhat backward incompatible - we propose to generate the click
>> event only when we are sure that there is no next click. In other
>> words, the partial clicks would not be delivered at all, the final
>> click would be a bit delayed. The pressed/released events would of
>> course be still delivered normally, with the correct clickCount value.
>> Any objections?
More information about the openjfx-dev