- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm working on a project with several people, but the single TopDesign.cysch files is extremely problematic for version control (git).
I'm trying to figure out how to use multiple .cysch files in one project. I realize that you can create multiple tabs or pages in a single .cysch file, but that doesn't help with version control since it seems that even with multiple isolated pages, TopDesign is not really mergeable.
Has anyone had success in separating out the various components of their design into multiple .cysch files?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your question kind of answered itself: we make components inside projects to split out complexity. One benefit is easy configuration options for the component. i would think they would version well in git.
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your question kind of answered itself: we make components inside projects to split out complexity. One benefit is easy configuration options for the component. i would think they would version well in git.
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I renamed TopDesign.cysch to something else and DID add a second .cysch to the project using add existing
after I created it. However, although it is IN the project tree, it is ignored when I build the project, even though I have Build Customizer checked on the top of the menu when I right-click there.
Is this a bug, or is there some missing magic?
Also, I can't move it up the tree in the explorer window. It is after the source code!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you found a solution to splitting up functionality for git? I'd love to have shared functionality in one schematic file and project-specific functionality in another.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
JoBr,
I don't know if this is an acceptable solution for you:
Creator only allows one TopDesign file,
When I need to have multiple design variants in the same TopDesign file I create the variant on a separate schematic page.
To switch between the different variants I first DISABLE the current schematic page.
Then I ENABLE the desired schematic page.
"Engineering is an Art. The Art of Compromise."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like disabling the schematic page modifies the .cysch file, so that wouldn't work.
The goal is to split up functionality so I can commit shared code into one git repo and project-specific code into another, (maybe using subtree or something like that), so when I make improvements to the shared functionality, it is automatically applied to all projects. Currently I have them all in separate linear branches and I have to manually make the same changes to each, which I don't always remember to do and which clutters their commit history.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
JoBr,
Theoretically there is a another way to solve this. However, I'm not sure you're going to like it.
Solution: Create custom components for circuit blocks with their own schematic sheets.
Using a custom Component library allows you to share these circuit blocks across a TopDesigns that use them.
If you need to modify the circuit block (hence the component), just make the changes to the component schematic. The changes will 'ripple' to all the TopDesigns using this shared component.
Using a component method, you can actually create multiple versions of the component for better version control maintenance.
"Engineering is an Art. The Art of Compromise."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's a good idea, thanks. The main schematic could just be a "block diagram" and the functionality hidden inside the blocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content