I’m mostly loving OmniOutliner 5 Pro. I’ve used OO since version 3, but when it comes to row spacing, OO5 is a step backward in my opinion. I used OO’s “spacing before” and “spacing after” in every outline, on every level. It allowed nicely-formatted outlines. It was simple, direct, and it worked.
“Above children” and “Below children” are both confusing and frustrating.
It takes WAY too much time experimenting. Every time I try to adjust spacing, I have to select the rows, set the value, then click the last child item, hit return and immediately backspace/delete to see the result. Worse, the setting isn’t applied to existing rows unless I do that click-return-backspace for every single row on that level.
As an example of the extra work it causes – let’s say I finally get Level 2’s children set (which are really level 3), so there’s some space between the last L3 row and the next L2. Now I’m typing and add an L4 – and instantly the spacing is wrecked. Now there’s extra space between L3 and L4, and no space between L4 and L2, so I have to select all the L3 levels and do “Before/After children” to set the L4s, and also select the L2 levels and do “Before/After children” to re-adjust the L3s.
All of that could be done with one setting: spacing above Level 2.
Seriously, this is so much added user friction!
And row padding adds to the confusion – because you can’t specify top vs bottom padding, spacing ends up looking inconsistent. A list might look nicely spaced with padding, but the moment you add a child item it gets wonky and you have to go through all that formatting of the child level to get it back where you want it.
A word processor gives you “before paragraph” and “after paragraph” for a reason: it’s intuitive and it works. It is much clearer to format by specifying what happens to a row, than to constantly adjust and re-adjust the rows above and below it.
This could all be solved by giving us back two simple options: space before and space after.
As a longtime user of Omni apps and an avid outliner, I implore you to consider restoring this feature.