While the provision of the ability to import assorted types of file formats is not devoid of merit, I would personally suggest that Altium should at least ensure that it *properly* supports all of its "native" file formats.
*Maybe* things have been fixed since then, but with AD4 SP4, there definitely were "issues" with saving a PCB (document) file in ASCII format, and reopening such files again (after they had been closed). *None* of the properties of any Embedded Board Array objects (such as their XRowCount and YRowCount properties) contained within PCB files were specified within ASCII format (PCB) files - meaning of course that all such objects were *not* "restored" (at all) whenever such files were subsequently reopened. There were also issues with "non-classic" Dimension objects; "Embedded" objects were used to specify some of the details associated with each such object - but the strings specifying the values of those Embedded objects typically contained "non-Notepad friendly" characters. This meant that if you opened an ASCII format PCB file in Notepad, made one or more legitimate changes to the contents of that file (such as changing the value of a "free" object's Layer property, as one illustrative example), saved that file (in Notepad), then reopened that file in Altium Designer, then there was a good chance that the "non-classic" Dimension objects in the file would either be corrupted or else "missing in action" altogether. But wait, there's more. :-) and :-( Whenever an ASCII format PCB file was reopened, a dialog box was invoked at the time prompting the user to specify the locations of the PCB's border. The associated details *are* in fact saved to the file in a satisfactory manner - but they were (and still are?) *not* being "reloaded" properly afterwards (and hence the dialog box at that time). That aspect *had* been fixed at one stage, but was subsequently "reincarnated". (Hint to Altium: The set of regressive tests run after each new build should include at least one instance of opening an ASCII format PCB file. If the border of the PCB can't be "restored" without "drama" at that time, then the subsequent invocation of the dialog box will result in each such particular test failing - and hence signal if there currently is a problem with ASCII format PCB files in this regard.) It would perhaps be excusable if there were issues associated with importing (or exporting) files of a "third party" nature, because there could be "translation" issues in such circumstances. But there is no excuse for not being able to save Altium-created files in ASCII format and then reopen them afterwards (and without "issues"). This situation encapsulates many of the issues concerning Altium Designer in general. There are many instances of functionality being provided which are "nice" or sometimes even useful to some extent, but which are still not of a "core" or "critical" nature - but at the same time, functionality which really is of a "core" or "critical" nature is sometimes significantly compromised. A case could be made that new features and functionality need to be provided with at least new major versions (though they are also often provided in service packs as well) for marketing reasons (and regardless of how useful such enhancements really are in practice). That said, I genuinely believe that failing to rectify issues and shortcomings which *really* matter, or "reincarnating" formerly rectified issues, or other instances of regression, definitely undermine marketing (and sales) efforts. It is possible to spend so much time debugging and "polishing" an application that it is either never released at all or else is only released in an "untimely" manner. The evidence suggests that Altium could be very close to the *other* extreme of "quantity, not quality", and when there are significant delays between service packs or major versions, it could be because the source code is so buggy that any changes made to it need to be followed up by rectifying bugs that were created (or else "uncovered") as a consequence of the previous changes. It would perhaps be understandable if Altium was operating in an extremely competitive commercial environment, in which any delays in "going to market" could result in a loss of market share - but as it is arguably *not* operating in such an environment (and is subsequently far less subject to such pressures), it would be prudent for it to at least tend to the "core" and "critical" functionality in a satisfactory manner, to avoid the outcome of fouling its own marketing efforts (and cash flows). Will they take this feedback on board? Who knows? Some people (and companies) excel at hearing what they want to hear (rather than what was really said)... Regards, Geoff Harland. [EMAIL PROTECTED] > Stephan > > If you can not find "Protel" compatible files and OrCad files are avaliable, you can always read the Orcad files. I recently downloaded a series of Samtek footprints that were in Orcad. They imported with no problems. You will find that Protel is one of the few programs that imports many formats. I know of no other program that has this many translators built in. > > Mike Reagan ____________________________________________________________ You are subscribed to the PEDA discussion forum To Post messages: mailto:[email protected] Unsubscribe and Other Options: http://techservinc.com/mailman/listinfo/peda_techservinc.com Browse or Search Old Archives (2001-2004): http://www.mail-archive.com/[email protected] Browse or Search Current Archives (2004-Current): http://www.mail-archive.com/[email protected]
