Hi Scrivener team,
As well as there’s the possibility to define separators for folder and text documents (and its 4 combinations), would you consider to include specific separators for document containers too?
In order to keep the interface clean, a double entry table might be used to specify the desired separator on each case. Something like this:
What do you think?
This sounds like a very good idea to me.
Before I put it on the list for consideration (I quite like the table settings UI idea), could you please give me an example of where this might be useful - that is, where you would need more separator choices than are already available?
Thanks,
Keith
Glad to do so, Keith. I have thought of several uses for this, but I’ll try to explain the simplest case.
I’ve found that Scrivener allows for a pretty good level of story structuring, not only outlining. For instance, I use 1st level folders for parts, 2nd level folders for chapters (just like the NWP template suggests). Then I use containers for scenes. Any actual text documents are within a container and belong to a single scene, never nested.
I’d like to be able to apply a separator among all scenes that exist on the same chapter, which in this case is just in the middle of the sequence text - container at compile time.
Since the current separator options only allow to differentiate among folders and texts, I cannot do it.
I hope this explanation makes sense. 
I’m a little confused about what’s in the text containers, if they represent scenes but contain text documents - do you mean the text documents are parts of the scene, smaller units of the scene, that would perhaps just have a line break separator between them? If so, as Ioa has just pointed out to me, we’ve been thinking about a solution for that sort of thing, and your suggested solution is a lot simpler than the one we came up with (which involved being able to set separators via meta-data, per-document). I think it’s a good idea and have added it to the list for the next major update. I can’t promise anything because of how enormous that list already is, but I definitely like the idea and the grid suggestion.
Thanks and all the best,
Keith