On 1/5/22 14:11, Dylan Simon wrote:
> Then it will look like this (I'm inferring, haven't actually tried it):

I'm still not quite following, but does the attached patch address the 
problem?