Corkaround works for me. It’s a good trick, but it does have its limits, particularly where you want to see a full multi-level view of the Draft outline that excludes anything not meant to be printed. You can use the outliner, but as with all “multiple selection” views, it will be flat and immutable as a list.
Quite right, but we feel the solution should be to mark that item somehow rather than hide it. I suppose the best way to explain why is to point to something just mentioned, how multiple selections behave and why they do. The ability to drag things around inside of a multiple selection, or into them, is disabled because it cannot be relied upon that there will be a logical place to put the dropped item. What is between “A” and “B” that we cannot see at the moment? It might even be six levels of hierarchy between the two. Does the dropped item get placed next to “A”, six levels deep, or right above “B” back at the top level?
It would follow that a similar way of viewing the Binder, with elements not being displayed between other elements, would have to be a “read only” list. As with the various uses of a multiple selection, it would have its uses, but it wouldn’t give you much you don’t already have in the main editor split (where incidentally in Outliner mode you can add the “Include” column and have immediate access to that information, including bulk operations where you select several and Option-click on any one of the checkboxes in the selection).
Secondly there is the reason for why Multiple Selections are flat lists. It’s one thing to flag some discarded scenes inside of a folder as not part of the Draft, but what if the folder is excluded? Do we draw the one item that is visible to compile, indented for no reason (or confusingly, as a child of the item above it by happenstance)?
You could achieve a very similar list in the sidebar, using Project Search to only find Included items in the Draft, and then search for “*”. There is your filtered flat sidebar view, save it as a collection and you’re good to go—if that approach is something that works for your outline of course.
All around it is less complicated, and potentially far less confusing, to draw these excluded items in a different visual fashion so that their status can be seen, without disturbing the visual continuity of the outline or raising impossible to solve situations over how item movement should be handled.
Hmm, I am not sure if that approach entirely responds to what you are looking for, since it seems in part not only the visual treatment, but how easy it is to toggle this condition (crumpling vs. clicking a bunch of buttons). Toggling the state of a document will be easier in the new design as well, hopefully that along with no longer needing to set a second meta-data value to create a visual effect, may bring things a little closer though.