Too much undesired zoom out

[Mintactus]

Hi

Deleting a relationship trigger a zoom out and therefore make arrows.app not productive at all.
Also when you add or duplicate a node it would be nice to have appear in your current view instead of zooming out in having the duplicate on the top of the chart.

[apcj]

Hi @Mintactus thanks for the helpful feedback. I have to admit that most of the testing we've done has been with relatively small graphs where zooming out is not so annoying, but I can imagine it would become a problem for larger graphs where you are working zoomed in quite a lot.

We could certainly change the behaviour on deletion. However, I'm not sure how to deal well with duplication. The current behaviour is designed to avoid the new elements overlapping with the existing elements. If we keep the new elements within the current viewport, do you have any suggestions for how to choose their position to avoid overlap?

[Mintactus]

Thank you for the feedback, Some software always use the top right corner of the actual viewport. Yes overlapping is possible but at least the user always know where to find it's duplicate

…

On Tue, Mar 1, 2022, 3:16 AM Alistair Jones, ***@***.***> wrote: Hi @Mintactus <https://github.com/Mintactus> thanks for the helpful feedback. I have to admit that most of the testing we've done has been with relatively small graphs where zooming out is not so annoying, but I can imagine it would become a problem for larger graphs where you are working zoomed in quite a lot. We could certainly change the behaviour on deletion. However, I'm not sure how to deal well with duplication. The current behaviour is designed to avoid the new elements overlapping with the existing elements. If we keep the new elements within the current viewport, do you have any suggestions for how to choose their position to avoid overlap? — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHIBVDLAI2YLT3NVQNFLZOTU5X4AJANCNFSM5PJHIP5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[guntarsTB]

+1 The same problem here!

[DanChristos]

I also +1 to this. I find it quite distracting to be zoomed out with every change I make. @apcj a possible suggestion for handling the adding of new nodes would be to auto re-jig any of the neighbouring nodes. You already have the snap feature, you could possibly auto-snap overlapping nodes.

Also what comes to mind, would be if you were to keep track of the node that the user most recently interacted with, the new node could appear within the vicinity of the recent interaction, rejigging neighbouring nodes.