| ??? 08/23/10 18:03 Modified: 08/23/10 18:22 Read: times |
#178248 - I gotta say, why haven't you told the makers? Responding to: ???'s previous message |
I have noticed the same problems and I whole heartedly dislike parts of EAGLE. You make a good point with
Richard Erlacher said:
there's a huge set of libraries, within which components are contained, but until you guess which library is "the one" you might as well build your own symbol. I have actually had to use a ULP to export all data about all the libraries and then use Microsoft's "findstr" (which finds text within multiple documents) just to get the proper package pad landing so that I wouldn't have to draw it myself. This was purely because EAGLE's search function just does not work at all. Now if they just had a single library for packages, all would be quite lovely. EAGLE's website contains this zip file with the ULP generator for your libraries, but the guy who made the search program wasn't even as good as Microsoft's. So, perhaps, the best solution would be to have someone come up with all packages and put them into a single library and I bet this would solve your issue? Then when you do decide to create the schematic symbol, you already have a package to choose from? I would like this. This would also address the issue Richard Erlacher said:
it shouldn't be necessary to modify the schematic symbol just because a package change is required to make the layout work or to respond to changes in availability or cost of components. Because you can just use the Change icon and select technology or package. |
