Skip to main content

Continuing the discussion from Paste to Replace sometimes causes the object to shift position:


When I’m trying to Paste to Replace a screen that’s currently connected within a flow (AKA there is an arrow that connects to it before, and it has an arrow connecting it to another screen afterwards), the connecting arrow from the replaced screen suddenly makes position of the arrows go weirdly up. I have to always double click the arrow to reset it to the original position.


Noticed it affects comment pins, too. I tried to Paste to Replace a screen that had a comment pinned on it, and after replacing, it displaced the comment to somewhere to the left. It’s happened every single time I do Paste to Replace that it’s getting a bit annoying ☹

Hi @ChiSenires do you have a video example of the issue you are seeing with Paste to Replace with the flow arrows?

Here’s a recording of the behavior: FigJam arrows going wack after Paste to Replace


I tried it with normal FigJam elements like the shapes and it doesn’t seem to do the same behavior as what I experienced. What I was trying to do initially was to put together a visual connected flow on FigJam using mockup screens from a design I’m working for. It seems like the behavior shows up if the element has a lot of arrows connected to it?


My expectation was that the arrows would just stay in place if it was placed within the component / screen but as shown in the video, it makes the arrows go up and down extremely.


Hope this helps 🙇‍♀️

Hi @ChiSenires thank you for that video! I was able to reproduce this only when the layers are within a Section. I’ve passed this information along to our engineering team. It looks like as a workaround you can move the content out of the Section and then perform the paste to replace and move it back if needed.

+1, this happens with me as well. Thanks for the tip to move content out of a section then back. But this kind of _partially_ defeats the purpose of saving time with Past to Replace over reconnecting arrows. That got me on the fence on recommending FigJam to the team for flow mapping purposes.

Hi ​@Mike_Ramos2 

 

Thank you for bringing this issue to our attention again. I've passed the information along to our engineering team, and in the meantime, please use the workaround Ryan shared.

 

Thanks for your patience.

Toku

Reply


Terms & ConditionsCookie settings