No event dispatched when moving nodes or connectors using the keyboard

[Mariano Ruiz]

Hello,

The diagram component has an event called positionChange that emits when dragging an element with the mouse. When moving the element with the keyboard ("nudging"), this event is not emitting. It would be useful to emit an event indicating elements have moved, preferably in this same event. In our application it is a requirement that we can identify such an event.

Here's a very simple example that logs to the console each time a node is moved. Note that when it is moved using the keyboard, nothing is logged:
https://stackblitz.com/edit/github-xpv7ym?file=src%2Fapp.component.ts

[Moulidharan Gopalakrishnan]

Hi,

Currently, the "positionChange" event is triggered only for interactive actions, such as when a node is moved with the mouse, and not programmatically through keyboard events. However, we will analyze the possibility of achieving this with keyboard events and update you accordingly.

Regards,

Moulidharan

[Moulidharan Gopalakrishnan]

Hi Mariano, 

Reported Issue: Position change event not triggered for Keyboard nudge commands

We can reproduce the issue and confirmed this as a defect. We have logged a defect report for this issue. We will fix this issue and provide the patch on October 29th 2024 weekly patch release. 

Feedback link: Position change event not triggered for Keyboard nudge commands in Angular | Feedback Portal (syncfusion.com)

Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.


Best Regards,
Moulidharan

[Moulidharan Gopalakrishnan]

Hi,

We are glad to announce that our Essential Studio® 2024 Volume 3 Service Pack Release v27.2.2 is rolled out with the reported bug fix and is available for download under the following link.

Essential Studio 2024 Volume 3 Service Pack Release v27.2.2 is available for download | Announcements Forums | Syncfusion

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.

Root cause: The issue occurs because the event arguments (keyArgs) are not defined when moving nodes or connectors with keyboard keys. Unlike mouse-based actions (e.g., dragging), where mouseArgs are properly assigned and trigger position change events, keyboard actions lack the necessary data to fire the event, resulting in no event being dispatched.

Regards,

Moulidharan G