Hi Werner, I have thought a very long time about your idea and came to the following conclusion:
1.I think, it's very complicated for new users to understand this mechanism. It's not intuitive and you need to document it in a manual. No hacker likes to read manuals. 2.It needs a lot of programming work on different places in the software (who is going to do this, and more important: who fixes the bugs in long term) I prefer the following way: 1. I copy all attributes to the schematic with the following command: (promote-invisible "enabled") 2.Check whether the symversion attribute in the schematic database is the same as on the symbol. Up to now, I haven't tested this function in the new gschem release, but I hope it works fine for my requirements. 3.Replace manually the symbol if needed. Some people would now argue: Some attributes should not be changed by the user. My suggestion for this is to introduce a âprotectâ flag and make this attribute non changeable. This gives the user the freedom to see all attributes and prevents new users for making mistakes by changing the wrong attributes. What do you think of this? Peter Am Donnerstag, 13. Januar 2005 18:31 schrieb Werner Hoch: > On Thursday 13 January 2005 00:05, Peter Kaiser wrote: > > > Someone mentioned a separate attribute dialog in the geda-user > > > list. It may look like this: > > > -------------------------- > > > already promoted attributes: > > > refdes= [textfield containing "U?] [deletebutton] > > correction: > refdes= [textfield containing "U?] [promotebutton] > > if the textfield is empty, delete the attribute > > > > ..... > > > ..... > > > availlable attributes inside the symbol: > > > symversion= [textfield containing "1.0"] [promotebutton] > > > ..... > > > .... > > > possible other attributes: > > > value= [] [promotebutton] > > > model= [] [promotebutton] > > > ----------------------------- > > > > Interesting idea. > > > > How do you want to handle this? Are all attributes always in the > > schematic database? > > I guess that, haven't looked at that yet. You can show all invisible > attributes. At the moment you can not access them, but they're there. > > > Or will the attribute be removed from the schematic database when you > > press the delete button? > > Only the attribute of the component. It will still exist inside the > symbol. > > > Is it copied from the symbol to the > > schematic when pressing the promote button? > > Yes, that is the idea. > After promotion the attribute will be inside the component and still > inside the symbol. > It will be the same kind of action, that you can use to overwrite an > existing footprint for example. > > regards > Werner
