Ohh, I like this ideaâŚ
I often array gems as block instances, then I can add prongs to the block - but this doesnât account for curvature of the surface itâs orienting to. So this âbetweenâ option would solve that nicely!
Hi, it works well in the latest version, but the Expand/Collapse state isnât saved; it resets to âExpandâ when restarting the command. Thanks..
That was intentional as hiding things from users is tricky for us as they often forget how to get back to where they were and call support and this command requires clicks in different panel sections to go.
Letâs see how this condition plays out and we can go from there. Itâs not hard to make it remember for the session if its a wide spread issue. I made a pass through today and pulled out a bunch of padding and freed about about another 100 pixels vertically. That will roll out in the next wip.
Thank you for preserving the old method, and please donât remove it in future releases! I see how the new tool is useful, but it is also overly complex in some use cases. I just wasted significant time trying to array an object, and the tool defaulted to rotating them rather than preserving the original objectâs orientation. My guess is that it was following the World orientation rather than the C Plane orientation. Being able to specify this would be very useful when working on projects that are not set to the standard World XYZ.