TI'm trying to create a sub-project, holding just a few topics from my main project.
I've read the docs and know that there can be a domino effect as linked topics are pulled automatically. So, I carefully removed all connections from the topics I want to link before importing into the sub-project. Didn't matter. My whole main project got copied to the sub-project. I'm starting to wonder just how little it takes to set off the dominoes. Does Flare see that Topic A uses Style.css and that Style.css is also linked to Topic B, so better bring that too? Has anyone had success creating a linked sub-project without getting a full copy of the main project?
Linked projects
-
BedfordWriter
- Sr. Propeller Head
- Posts: 231
- Joined: Wed Jun 23, 2010 10:13 am
- Location: Nova Scotia
Re: Linked projects
If you don't want this to happen, then don't select Auto-include linked files in your project import.
If you want to have precise control over which files are imported, then I'd recommend using a condition.
Create a new condition and set that on all files that you want to import.
Then in your project import, set it to include all files (*.*), and for the Import conditions set it to Include your condition, and tick Auto-Exclude Non-Tagged Files.
Using this method, you only import files marked with that condition.
If you want to have precise control over which files are imported, then I'd recommend using a condition.
Create a new condition and set that on all files that you want to import.
Then in your project import, set it to include all files (*.*), and for the Import conditions set it to Include your condition, and tick Auto-Exclude Non-Tagged Files.
Using this method, you only import files marked with that condition.
-
BedfordWriter
- Sr. Propeller Head
- Posts: 231
- Joined: Wed Jun 23, 2010 10:13 am
- Location: Nova Scotia
Re: Linked projects
Editing my own post. Now that I understand things better, I don't want to leave bad information on the forums.
The problem I was running into was the automatic re-import before compiling. During the first import, Flare gave me a list of files that matched the set condition and I deselected all but the few I wanted. My mistake was in thinking that this selection would be remembered.
On compiling the project, Flare did a fresh import as directed. But, this brought all the files that matched the conditions set in the import and, being automatic, did not pause to let me deselect all but my chosen few. Hence, I ended up with the entire parent project being copied to the child.
The real trick, as Dave pointed out, is to set a conditional on the desired files in the parent project. The automatic re-import to freshen the files in the child project will then bring only the files I wanted.
The problem I was running into was the automatic re-import before compiling. During the first import, Flare gave me a list of files that matched the set condition and I deselected all but the few I wanted. My mistake was in thinking that this selection would be remembered.
On compiling the project, Flare did a fresh import as directed. But, this brought all the files that matched the conditions set in the import and, being automatic, did not pause to let me deselect all but my chosen few. Hence, I ended up with the entire parent project being copied to the child.
The real trick, as Dave pointed out, is to set a conditional on the desired files in the parent project. The automatic re-import to freshen the files in the child project will then bring only the files I wanted.