On 01/01/2010 07:03 AM, Vincent van Ravesteijn wrote:
it seems the master changes according to the last-loaded master.
Also, when closing one of the two masters, its child is also closed.
This is expected, basically, at least the first part. That the child
closes whichever master closes is wrong.
Here I'm not understanding: why are children closed when their master
is closed ? Suppose I'm working on a.lyx and b.lyx, with a including
b. After a while, I decide only b needs further changes, then I save
and close a, but also b is closed -- this puzzles me a bit.
I guess the rationale is that we open all children automatically too.
So, if you're working on a multi-part document, you'd only have to
open the master to have all children, but then it's convenient that if
you close the master you'll also close all children.
The other rationale is that, if the child is open as a child of the
master, then there are lots of things in the child that depend upon the
master. That is partly why there is the option of "hiding" the master.
So, if you can think of an intuitive way of handling this.. let us
know. Maybe, we should only close the hidden children (the ones that
were not explicitly opened by the user). Maybe, we should ask the user
whether he wants to close all children (and have a 'do not ask again'
checkbox). Maybe, we should have two options for closing a master
buffer e.g., Close Master and Close Family.
But if the child has a default master, then this does not work, because
the child wants its master open. Obviously, one could check all of this,
but it's messy.
Perhaps the options to have are: Close Family and Hide Master.
rh
