I don't recall if I was supposed to reply to all or just the
lists.lyx.org<http://lists.lyx.org>. My apologies if I did it incorrectly.
spitz, jrioux, thanks for your prompt comments.
I agree that the child document becomes it's own standalone entity when
compiled by itself. Thanks for that insight.
My ulitimate confusion (and I know many of my co-workers will have the same
problem) is that when a branch is advertised with a checkmark (ON) or an X
(OFF) in ANY document, the expectation will be there that it will display
accordingly in the compiled output. After enough fiddling with this I now know
that you have to take this inline information as only being related to the
master document (UNLESS it says "child only"). It has to be ignored when
dealing with a child document on their own and one must go to Document >
Settings > Branches. I found it confusing to have branch shown as ON and OFF
at the same time in different places without having any clear indicator as to
who owns what. Then I found myself right clicking a branch into the ON state
from WITHIN the child document, AND the effect seems to propagate back to the
master. Likewise the child seems to inherit the state when the change is made
in the master. But, as you point out, nothing is really inherited, it was only
an illusion which was lost once I realized what it all means. Indeed, it's all
consistent and working properly.
May I suggest displaying information as follows:
Have the inline display of branch information in a CHILD document to do
somehting like this: (v is supposed to be a checkmark, indicating the branch is
ON, x indicates the branch is OFF)
1. Branch (x master only) A:
2. Branch (v child only) B:
3. Branch (x master,v child) C:
For an A branch defined only in the master (in this case OFF), a B branch
defined only in the child (in this case ON), and a C branch defined both in
master and child (OFF for master, ON for child). Item 2 is basically already
implemented in LyX 1.6/2.0.
Some suggestions on right clicking
- Right click on item 1 and you are given the choice to ADD the branch to the
child document, and to turn it on or off.
- Right click on item 2 and you are given the choice to turn branch B on or off.
- Right click on item 3 and you are given the choices to change the state of
the master C branch or the child C branch.
Had it been something like my suggestion I don't think I would have been
confused.
As we transiton to LyX 2.0, I will make use of the includeonly feature. But in
the last year most of my co-workers (more of a MS word crowd with no TeX
experience) have gotten in the habit of frequently compiling their child
documents to read their final output as part of the editing process. I suppose
for that I can define all children to have all the branches turne ON so at
least everything can be read immediately during editing. For distributing
individual chapters, we can start using includeonly.
Thanks.
On Jun 20, 2011, at 9:57 PM, LyX Ticket Tracker wrote:
#7636: Document Branches spanning master docs and included files don't work
properly
--------------------------+-------------------------------------------------
Reporter: marutgers | Owner: spitz
Type: defect | Status: new
Priority: normal | Milestone: 2.0.x
Component: master/child | Version: 2.0.0
Severity: normal | Keywords:
--------------------------+-------------------------------------------------
Comment(by spitz):
This is a conceptual question. When they are compiled separately, children
are no longer children, but separate documents. Hence they should not
inherit any setting from other files (even if those are their "master" in
other contexts). So the current behavior is correct. It's also a good way
to branch things out in documents that are only to be shown when these
documents act as children (I use this feature all the time).
As to your problem. There are basically two ways to proceed:
1. In order to easily import the branches in the child's setting, hit
"Undefined branches" in the child's Document > Settings > Branches and
import the branches by a simple click.
2. If you want to export/distribute individual chapters from a larger
project, the way to go is not to compile children on their own. Instead,
use the "includeonly" feature, i.e. go to the master's Document > Setting
Child Documents, select the desired child(ren) and compile from within
the master. This will also give you the correct counters and references.
--
Ticket URL: <http://www.lyx.org/trac/ticket/7636#comment:3>
The LyX Project <http://www.lyx.org/>
LyX -- The Document Processor
Maarten Rutgers PhD, Staff Scientist
Asylum Research
6310 Hollister Ave
Santa Barbara, Ca 93117
tel: 805 696 6467 X294
fax: 805 696 6444
www.asylumresearch.com<http://www.asylumresearch.com/>
