![]() ![]() ![]() From a legal perspective, you have to define how you want to apporach the problem. I never got any negative replies from Altium. Did Altium ever try to sue you or something like that? Look how tracks are added, how the record looks like, what parts of the file got updated,…ĭo you mind sharing your work? I think that I will give it a shot but before that, I should consult a lawyer, I’m not completely sure what the German law thinks about I liked your presentation it is kind of an inspiration for this project.Check how much the file differs in those four versions (how stable it is).Create another new empty project and save it.Close the program, open the file again and save it.Then export many files with known informations: If you want a binary importer directly, create lots of ASCII exports to get a clue how the file-structure might look like.Settle for ASCII import for the beginning (as done by Altium, etc.), as a binary importer should be able to build on top of this work.If you want to build an importer, those would be my hints: Building a binary parser looks quite challenging after my first try. After that it got out of alignment as the records had different sizes. I was able to extract some track information, but my parser was only able to parse three or four tracks in a known data segment. I have to say, my work is only based on existing files and the existing viewer, as I do not own Allegro. I was able to extract some fundamental informations (data-types for coordinates/angles) but not much more. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |