draw.io sizing and layout
The one thing every draw.io migration loses is the macro's authored width and height. Every migrated diagram is created at a standard height instead.
How it then renders depends on one option, and unusually for this product, that option can be changed in bulk afterwards.
#The two layouts
Setting | How diagrams render | When to use it |
|---|---|---|
Auto (default) | Scaled to the column width | Most documentation, where consistency reads better |
Classic draw.io layout (beta) | The size and left alignment they had in draw.io, in a frame that hugs them | Estates where diagram size was chosen deliberately |
This is the one migration decision you can change your mind about in bulk. The Repair diagram layout tool switches migrated diagrams between the two, and only writes where the setting actually differs.
#What is not covered
The classic layout option is not applied to zero-egress embed references. Treat that as an observed limitation rather than a designed behaviour.
The repair tool covers the Diagram and Diagram Reference macros, but deliberately not the Diagram Source macro.
Other Capable diagram macros are counted separately and left alone, because writing a layout onto them would silently opt them out of the space default they inherit.
#The border
The draw.io border option is not carried across. Capable's own border setting is available per macro and as a space default.
#A few things that catch people out
Migrations run before the layout option existed all landed on Auto. That is what the repair tool was written for.
The repair tool has no preview and no check step, so the fix-one-page-first gate is its only safety net.
Its log matching is loose, so expect candidate rows that scan to nothing.
#Related
The one choice you can change afterwards.
