Krank

I really like the "auto grid" feature of Designer, where the grid "subdivides" based on zoom level. However, it's kind of annoying that the feature jumps between using 5 and 10 subdivisions… Five: Also five – but note that the one "big" square is now four… And there's now a major grid line in the middle of what used to be the center rows/columns of sub-grid squares. Suddenly 10: What I would like: For my own workflow, I'd like to always use subdivisions of 4 or 8. That would keep the main divisions from jumping around between zoom levels. But I think the ideal would be some way to customize this behavior as a user – both the subdivisions and how the primary grid squares subdivide when zooming. As it is now, I have to disable the auto grid and do the same runaround as on Illustrator: Zoom in, go to the Grids and Axis Manager, manually change the spacing (working with powers of 2 for convenience), then do whatever I zoomed in to do, zoom out, go to the Manager, change the spacing… So… please give some love to the auto grid? 😃 I really like the idea of a grid that works based on the current zoom level, but I currently struggle to make it work for me.

Currently, as far as I've been able to ascertain, it works like this: Let's say I create a symbol. Call the symbol ChildSymbol. Then I create another symbol, let's call it ParentSymbol, which included ChildSymbol as well as some other objects. All is well and good – making changes to ChildSymbol updates all instances of ChildSymbol, including those inside instances of ParentSymbol. If I select an instance of ChildSymbol and press "Detach", the object is detached and is now its own object, able to be edited without affecting instances of ChildSymbol. If I select an instance of ParentSymbol and press "Detach", that object as well as the instance of ChildSymbol it contains are now detached. The Detach action seems to propagate into all sub-symbol-instances. If there's no way to prevent this currently, I'd very much like one. In other words, I'd like to be able to Detach the instance of ParentSymbol without necessarily also Detaching the instance of ChildSymbol it contains. Symbols are a wonderful way to quickly make large changes, and being able to work freely with different levels and hierachies of symbol-instances would be very nice.