Re: [PEDA] Which library is used in UpdatePCB
Hi, I also think it works like Andrew describes, for instance as for my experience. I came across this behaviour already in version 2.8, when I was merging libraries from different developers. But, for normal working situations why not organise libraries in a way, that there are no different footprints with the same name in the PCB libraries? This avoids any unwanted effects of this kind from the very beginning. Regards, Gisbert Auge Jon Elson [EMAIL PROTECTED] on 16.07.2001 21:23:53 Please respond to Protel EDA Forum [EMAIL PROTECTED] To: Protel EDA Forum [EMAIL PROTECTED] cc: Subject: Re: [PEDA] Which library is used in UpdatePCB Andrew Ircha wrote: You're close but not quite there. I was making modification in one library, hiting UpdatePCB (which presents as a button in the explorer panel), and instead of putting my new, freshly changed footprint into the open PCBs, it was taking a footprint with the same name *from a totally different library* and using that instead - it didn't appear to be taking other footprints. It was ignoring my hard work :-| Yes, I think it searches the names on all open libraries in order, and takes the first match of that name, whether it is the newly edited part or not. Definitely a poor way to do things. In so many other cases, if there is a question about which thing you intend to change, you get a dialog box to select the right one. This is why it is a good practice to open libraries, place the parts, and then close all the libraries, and make a project library from the placed parts. I think I'd understand Protel updating *all* open PCBs with my new changes, even if it isn't a great thing to do, but it wasn't even doing that. It was taking the altered footprint's name, and updating my open PCB with a footprint from another library which happened to have the same name. Nasty. Yes, at least this behavior should be thoroughly documented, and suitable warnings given that this can cause unexpected results. But, your hard work isn't lost. It is still in the library part that you modified. If you close the other libraries that have interfering part names, and do the update again, it will work right. Jon * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * - or email - * mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: [PEDA] Which library is used in UpdatePCB
Gisbert Auge Wrote: But for normal working situations why not organise libraries in a way, that there are no different footprints with the same name in the PCB libraries? This avoids any unwanted effects of this kind from the very beginning. In theory very nice but the practical situation is sometimes different My sheet symbols have some 'default' footprints, this makes schematic drawing easy. If I place a 74HCT00 device I have two 'default' footprint fields 'DIP14' and 'SO14'. A lot of other stuff is also using the same footprint. Suppose that I change something in the PCB footprint then I have two options. -1- Save the changed footprint to another name and all the default footprint names in the schematic symbols are useless. -2- Change the component without changing the name, and live with the fact that there is a possibility to have two different components with the same name in the library cache. If the footprint is changed because there is a real problem with the old version, wrong dimensions or something, then I don't like option 1. It means that the wrong footprint is still available. Even if you delete it from the library then it might pop up from an old design and getting into the cache. There is an item in the knowledge base at www.protel.com Protel Knowledge Base Item ID: 1934 How does the component cache in Protel 99's schematic editor differ from previous versions? In Protel 99 all the component attributes' are compared as the components are being added to the cache, including the component name, graphic and text fields. If the components are not identical in every detail then both are included in the cache. This behavior means that in Protel 99 two components on a sheet can have the same name, but have different graphic and/or text attributes. It would be nice if Protel could give a warning if this situation occurs. It is not always a problem but I want to be aware of it when it happens. It would be even nicer if there is also an option to compare the internal cache and the library files. Suppose that I add some details to the silkscreen of a footprint to make it look nicer. Such a change is not critical for a design. I don't want to make changes in 'old' designs, but if I make a revision then I want to 'update' the 'old' footprint to the new 'nice-looking' one. If Protel could give a report option to compare the cache against the library, after loading a design, then it could point us the components which have the same name but are not completely identical. [Dream mode on] Load a file into Protel Start 'report library component compare' Protel reports: library component 'X' found # times. Version 1.5 and Version 1.6 Do you want to show them in overlay mode and highlight differences? After checking the differences, choose 'Update all instances to new version' or 'Update selection to new version' or 'Cancel' [Dream mode off] Aalt Lokhorst (e-mail [EMAIL PROTECTED]) address: Schut Geometrische Meettechniek bv Duinkerkenstraat 21 9723 BN Groningen, The Netherlands tel. +31 50-5877877 fax. +31 50-5877899 - Original Message - From: [EMAIL PROTECTED] To: Protel EDA Forum [EMAIL PROTECTED] Sent: Tuesday, July 17, 2001 10:04 AM Subject: Re: [PEDA] Which library is used in UpdatePCB * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * - or email - * mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: [PEDA] Which library is used in UpdatePCB
On 11:53 AM 16/07/2001 +0100, Andrew Ircha said: ..Snip.. You're close but not quite there. I was making modification in one library, hiting UpdatePCB (which presents as a button in the explorer panel), and instead of putting my new, freshly changed footprint into the open PCBs, it was taking a footprint with the same name *from a totally different library* and using that instead - it didn't appear to be taking other footprints. It was ignoring my hard work :-| I think I'd understand Protel updating *all* open PCBs with my new changes, even if it isn't a great thing to do, but it wasn't even doing that. It was taking the altered footprint's name, and updating my open PCB with a footprint from another library which happened to have the same name. Nasty. Yikes - if what you say is true (and I don't doubt it) it is a bug and a nasty one. Anyone care to confirm? I will wait until there is some conversation on the matter (or a few days) before I add it to the bug list. In the interest in sharing the load - is there someone else that would care to confirm this bug? Andrew - I assume you are quite sure you have assessed the situation and that we are not getting crossed wires here? I do not like adding things to the bug database unless they are clearly bugs. Bye for now, Ian Wilson * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * - or email - * mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
