You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2024. It is now read-only.
When a shape has a "click" event, the coordinates and position are in the output message (as expected):
However on a touch screen, the touchstart event will trigger a message without these two fields:
For the 2.0.0 release we should refactor the coordinate related fields in the output anyway, to have the same as the other UI nodes (see discourse discussion): we will try to use the same fields as the dashboard button sends. And perhaps again a legacy flag for old flows, to make sure they are not broken ...
The text was updated successfully, but these errors were encountered:
When a shape has a "click" event, the coordinates and position are in the output message (as expected):
However on a touch screen, the touchstart event will trigger a message without these two fields:
For the 2.0.0 release we should refactor the coordinate related fields in the output anyway, to have the same as the other UI nodes (see discourse discussion): we will try to use the same fields as the dashboard button sends. And perhaps again a legacy flag for old flows, to make sure they are not broken ...
The text was updated successfully, but these errors were encountered: