Parent and Child Views - A few thoughts from roadmap

[johndellostritto214]

Views when transferred from one sheet to another need some intelligence. What I mean by - Is the view being moved should  A) know its' size and destination B) know the size of the blank area it is being copied too. and the software logic will say hey I can copy here in this space with no problem. We lose so much time figuring out Why did the computer do "X" instead of "Y"?

To be able to copy ( parent - child)  views to multiple sheets that shows one minor difference would be a great asset in drawing productivity. Drawings are the communication tool for the assembler - he is the internal customer he needs the info from the new views to do his job. So making things clear and understandable is paramount. 

In MSword if you do not have enough space for a picture it jumps to the next sheet and then it takes 3 minutes to figure the largest size that can be copied  - that stays on that page. This logic is something developers need to figure out in F360 to save wasted engineering time experimenting with views. 

Thanks,

John

[johndellostritto214]

Another challenge is how to carry and "know" the drawing zone ( alpha, num)or sheet no. -  the view comes from including the open white space to place copied view.

[ClintBrown3D]

Hi John

Thanks for sharing. Some of what you have mentioned is in our longer-term planning. As always every customer request that we get, from meetings, emails, forum posts etc. gets collected and categorised in our feature request database. This information is used to prioritise the features that we build. I've added your requests to our database.

In the November release, we added "Duplicate Sheet" functionality, this will help with your workflow of creating another sheet, and making subtle changes. Here's a GIF of the new tool in action, link in the what's new post below.

https://www.autodesk.com/products/fusion-360/blog/november-2022-major-product-update/#Drawings