If a node has a collapse attribute, and it's value is "true" -- when the worldoutline displays it, its subs are not visible.

Nodes in outlines can have attributes, which determine how the node is processed by the worldoutline software. Attributes can be used for many other things. They're a very core idea not just to outlines, but to software in general.

Dave, an old friend and fellow developer, felt strongly that the expand/collapse state of an outline, when displayed, should be a function of whether it's expanded or collapsed in the outline on the destkop, when you're editing it.

I strongly disagree. That form of expand/collapse is there to support human work and ideation. If it gets used for rendering, then two things will happen: 1. You will inadvertently have something expanded that you really wanted collapsed. 2. You will not use expand and collapse as freely on the desktop whether or not you're using it in this case to control the display. It will make other things fragile, and therefore will cause you to trust it less. Both forms are important, and they are not the same thing, so you need two controls.

BTW, I think this is why Microsoft products work one way and mine work another. :-)

With much love and respect and no sarcasm.

opmlEditor.menuCommands.outlinerSetCollapse

system.menus.menubar

opmlEditor.data.worldOutline.rightClickMenu