While I am a major cheerleader for OmniOutliner, there is one area that is a source for endless frustration for me. I am working on a font inventory for my iMac and I am forced to apply styles on a block-by-block basis. For instance, I have Level 1 Rows defined with Avenir Next Thin 16 pt. The problem is that for the last two columns in a Level 1 row, I want to have a different appearance. The columns styles are defined as,
Classification(s) Avenir Next Thin 12 pt
Copyright(s) Avenir Next Regular 11 pt
The problem is that the column styles are always de-prioritized because the row style always takes precedence and there is no way to change the order for styles. Thus, in what will ultimately be a large document, I am being slowed down because OmniOutliner is dictating style priorities instead of letting me to define where and how styles are applied.
Named styles are also hit or miss. Just getting the attributes right for a named style seems to be inconsistent; I am witnessing the named style becoming deselected each time an attribute is modified. Applying a named style to a selection seems to easily fall prey to the same behavior I see with the document styles, where the named style applied to a selection is superseded by the row style.
While it looks good, OmniOutliner Help, offers little information. The help document is not searchable, and when the user happens upon the topic they wish to explore, the details are at best spartan; if any information is provided at all. In The Omni Group’s defense, much of OmniOutliner’s features are self-explanatory, but when I actually need to look something up, OmniOutliner Help seems to just gloss over many topics instead of providing in-depth details.