Skip to main content

I am having the same issue as detailed in the post https://lucidchart.zendesk.com/hc/en-us/community/posts/360077453331-Stop-connected-lines-moving-when-extending-a-line and wanted you to know that I am also hitting this a lot.  We have a lot of block diagrams connected with lines and often need to change the size of the block to be able to add or subtract some areas. 

 

However when we resize the object all the connections are stretch and usually ends up with overlapping lines and generally unusable.   It take a long time to adjust again. 

 

Knowing that the solution is to first disconnect the lines is not going to work as this is as much effort as fixing the lines after they are stretched.     This is likely enough for me to start looking for alternative solutions as I'm hitting this all the time.    Not a good design. 

Lucid chart would be so much better if connected lines stayed independent of the line being altered through the use of a key stroke. It's great to connect lines but if you want to resize one of them (or a shape they are connected to) generally one doesn't want the whole assembly to move with it! Surely there must be a way perhaps through a combination of keys to make an alteration to one component (line or shape) without the whole assembly it is connected to becoming dragged out of shape?


Hey Mark and Nigel thank you for posting in the Lucid community! Our sincere apologies for the delayed response on this thread--I wanted to follow up in case this answer may still be useful to you and to provide a solution for other users who see this thread in the future.

Thank you for your request! We're always looking for ways to improve Lucidchart and your feedback is the best way for us to keep developing a useful and effective product. I've submitted your idea to our product team on your behalf and it will be taken into consideration when prioritizing improvements.

For anyone else with a similar request: please submit your feedback using this feature request form to provide additional context and support for this feature request. We would also love to hear additional detail about your use case see an example of what you're hoping to achieve or learn about a workaround you've discovered in the thread below. Thanks for your request!