Hello Jean, That sounds interesting. Maybe one way to do this would be allowing nested \contexts? For example \layout { \context { \StaffGroup \context { \Staff something }}}
to specifically target contexts that are children of other context. This way it would be possible to have \new StaffGroup \with { \context { \Staff ... } } << ... >> @David: Hardly anything put into layout blocks can be but into paper blocks. For example something like this won’t work: \bookpart { \paper { \override Staff.StaffSymbol.thickness = #2 } { c d e} } Best, Valentin Am Mittwoch, 9. Februar 2022, 17:04:36 CET schrieb Jean Abou Samra: > > Le 09/02/2022 15:24, Kieren MacMillan <kie...@kierenmacmillan.info> a > > écrit : > > > > > > Hi Valentin, > > > > > Also this makes having different stylesheets for different bookparts > > > quite impossible. > > > > > > So I want to ask if there is any reason against allowing layout blocks > > > in books and bookparts, having them override the default layout for > > > that book or bookpart. > No idea. > > > > If not, would you consider it reasonable to do it this way. > > If technically sound, yes. > > > I agree we should have \layout options at all levels, cascading/overriding > > downwards > > > > top => book => bookpart => score > > > > [Are there any other places/levels it could or should appear?] > > I have a vague dream that it could also work in > intermediate contexts. Mock syntax: > > << > \new StaffGroup \with \layout { > \context { > \Staff > %% Consist in all staves of this StaffGroup > \consists Bla_engraver > } > } > << ... >> > <unaffected staves...> > > > Best, > Jean
signature.asc
Description: This is a digitally signed message part.