Restore default attributes

[n.smithHJCP5]

I'm not sure if this is a bug or a feature but at the very least I'm looking for a workaround. When I use the "replace" command on a schematic, some user defined attributes from the old part stick around for the new part.

I've got a library with a bunch of 0805 resistor values in it. I'll try to get all my terminology correct here. It's one component, linked to one symbol, one footprint, with one variant "0805". Linked to that variant are a number of attribute sets, one for each resistor value. In each attribute set, I also put in things like the tolerance, wattage, and an internal company part number. Here's what I'm working with:

Using the add command, I can find that 0 ohm resistor and plop it on the schematic.

If I were to use the replace command and choose the 1k to replace that 0 ohm I just added, it'll update all the attributes easy peasy. 

However, the problem comes when there is a user defined attribute. If I were to plop down that 0 ohm and change our internal part number to "#NONE"

THEN do the replace command for the 1k

That "#NONE" sticks around. 



Okay fair enough. But now there's no way to get it to go back to the default value. In the attributes window there's a note about it being changed [below]. But double clicking that PN field and changing it back to "default value" does nothing. I've tried clearing out the value field entirely then changing it to default value but it always just reverts back to the user defined value. There's no way to restore the default value from that window. 

[jorge_garcia]

Hello @n.smithHJCP5,

I hope you're doing well. The easiest way to restore the library values is to use Autoposition Attributes command and select the option restore default. Then click on all of the components you want to restore back to the library attribute.

Let me know if there's anything else I can do for you.

Best Regards,

[n.smithHJCP5]

Thank you for the response. However, I am still having the same problem. I'm using "Reposition Attributes" under the document tab. In the new window, I select "Restore Default". I've tried left clicking the resistor, right clicking and clicking "Reposition: Group", but none of it makes that "#NONE" go away. All that seems to do is move the attribute text back to its original location, not restore the actual library text itself. I'm using v2.0.17954 x86_64

I'm fairly certain the issue as described in my original post is a bug. In Eagle v9.6.2, the attribute window will change it back to the default value immediately upon clicking default value.

[jorge_garcia]

Hi @n.smithHJCP5,

If you do the same workflow in Fusion with the attributes dialog, does it work? I want to make sure you have a way to move forward easily.

It looks like it would be good to have the option for the Reposition attributes command to restore default attribute values. If you have any other ideas for how to simplify restoring the default value I'm all ears.

Best Regards,

[n.smithHJCP5]

---

@jorge_garcia wrote:

It looks like it would be good to have the option for the Reposition attributes command to restore default attribute values. 

---

I would respectfully disagree with that solution. That command is good for moving the text from attributes around to something a little bit more clean looking. It's also used if a user accidentally dragged the resistor name off screen or deleted the resistor value text. Lumping in a feature that would overwrite the actual data in there (e.g. renaming the resistor) is the kind of feature that should be kept separate.

How it worked in Eagle is sufficient. 
1. Right click resistor on schematic

2. Attribute
3. Double click the user defined attribute in question

4. Change dropdown box from "user defined" to "default value"

5. Program automagically changes the attribute from "#NONE" to "#470003" in my example

That works in Eagle. It does not work in Fusion. In Fusion, #5 does not happen. It just stays as "#NONE" and changes the dropdown box back to "user defined". The only work around is to just manually type out "#470003" as the new user defined value. But that requires the user to know what the correct value is. 

My vote would be for #5 to happen in Fusion as well. 

[jorge_garcia · Accepted solution]

Hi @n.smithHJCP5,

Then I agree, this is a bug, I'll file the bug report now. Thank you for your concise explanation.

Best Regards,