Hi, I need to find all pages including nested pages in a project.
Where do Kicad stores this information?
It looks like Kicad is storing each page (page path) inside the page that it is instantiating it.
It looks like it is not pretty trivial to parse all these pages.
Also, kicad_pro has a reference to these sheets, but it does not store the file path just the UUIDs. it looks like this is missing information there.
So, this information is pretty entagled withing the files.
Another complex thing is that each page stores the path of the hierarchical page inside of the page relative to the page path. And this is kind of crazy.
It would be so nice if a single file could store pages and pages path relativelly to the project path. =)
If you know root sheet path (should be stored in project file or it just has same file name sans extension) and if you can extract subsheets from kicad_sch file which should be simple with any s-expression parser then writing recursive function to extract them all will be ~10 lines of code.
Which particular part are you having problems with?
KiCad file formats are not the best and despite trying to be both human readable and easily machine parseable surprisingly fail at both in my subjective opinion.
But they are not bad either. Maybe when you do that kind of processing bash is not the best choice and something like python will make your task much easier.
Yeah, maybe. I have some stuff made with bash so I am keeping it. Right now I just have the list of files I want. My current struggle is to reference all of them from the root of the project but it is almost there.
Some projects are a bit complex in the organization. This is why most people prefer to keep Kicad projects as simple as possible since some tools/scripts may have a hard time trying to parse things required.
Looking inside the kicad_pro I see instances of the pages, with the page_name close to it.
It could count 10 instances, where some are the same (5,6) and (7,8) since they are replicated.
This file could definitely have the files path relative to the root of the project, too.
Here it shows the existing .kicad_sch files found with find and they may not belong to the project. They may just be inside the project’s folder without being in use. So I cannot trust on this.
And then here, I have my recursive parser where I have to reconstruct a usable path from the root of the project. Line 2 and 4 show things inside the sch folder, for instance, but the file_path found inside the schematics are not the same since they are based on the place where the current schematic sheet is.