Bugs: Losing attributes when moving components between schematic sheets v9.1.1

Anonymous

Bugs: Losing attributes when moving components between schematic sheets v9.1.1

Anonymous
Not applicable

A) Bug 1: When moving a group of components from one schematic sheet to another you seem to lose all the component >Names and >Values which can be recovered by using the old previously named Unsmash/Smash option.  But is very painful for a complex sheet move.

 

B) Implementation Problem: Which is now confusingly called "Restore Position" (of what? Attributes duh!) and "Reposition Attributes" and has been left as a ticked option called "Smashed"  in the properties dialog box.  I prefer the old Smashed/Unsmashed with perhaps a floating explanation popup that uses the other terms.  Smashed appears to be an industry-wide cross-application accepted term.  Single words are usually preferable over verb-noun style labels (even if someone has to learn them).

 

C) Bug 1 Related Symptom: If you move the components between sheets and then save and re-open (before correcting these) you will get a number of mysterious non-self explanatory text editor errors about missing attributes.

 

D) Bug 2: However, the real pain is not over as the "Restore Position" option (i.e. the workaround) does not reactivate without manual re-selection every single time from the right-click menu. Which is a bug because it goes against the Eagle traditional command use that allows these command to be repeated with just a single left-click on the component objects.  However, the reciprocal command "Reposition Attributes" (also likely required to be used for the tedious workaround) does work as expected in this way.

 

E) Feature Request: Some way to set the default >Names and >Values attributes (i.e. Size and Font etc) that override those set in the component library.  ideally, this should be done as a setting associated with the Schematic file.  And an option to set this by default on placement (or not) and also a command to reapply the default settings.  The need for this is highlighted by these bugs.   And is usually something people run ULPs to do regularly, but is best adjusted at the time of component placement.

 

F). Another related issue is that if Bug 1 goes unnoticed (easily done)  and the user removes the old schematic sheet the UNDO option does not seem to support the recovery of deleted schematic sheets.

 

0 Likes
Reply
1,020 Views
7 Replies
Replies (7)

Anonymous
Not applicable

Errors reported are like this
Loading C:\EaglePCB\...\XXXXXXXXXX.sch ...

 

Warning(s):

 

line 18296: skipped unexpected tag <attribute>

line 18297: skipped unexpected tag <attribute>

line 18298: skipped unexpected tag <attribute>

line 18299: skipped unexpected tag <attribute>

line 18300: skipped unexpected tag <attribute>

line 18301: skipped unexpected tag <attribute>

line 18302: skipped unexpected tag <attribute>

line 18303: skipped unexpected tag <attribute>

line 18304: skipped unexpected tag <attribute>

line 18305: skipped unexpected tag <attribute>

line 18306: skipped unexpected tag <attribute>

line 18307: skipped unexpected tag <attribute>

line 18308: skipped unexpected tag <attribute>

line 18309: skipped unexpected tag <attribute>

 

BTW: I did another test and the UNDO seemed to work fine on that run! So I guess it may have been something I did like close and restart the application.

 

0 Likes

Anonymous
Not applicable

See attachment for screenshot of problem.

0 Likes

jorge_garcia
Autodesk
Autodesk
Hi @Anonymous,

I hope you're doing well. This is extremely strange, I can't reproduce what you are seeing. When you refer to the >NAME and >VALUE attributes did you actually create in the ATTRIBUTES dialog NAME and VALUE attributes? You shouldn't do that normally since >NAME and >VALUE are built in variables and are handled special.

Maybe that is the source of these issues?

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

Best Regards,


Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

Anonymous
Not applicable

Hi:

No, I can assure you I am not setting attributes as you suggest.  I am rather experienced Eagle PCB user.

Version 10.0.17134 Build 17134

Processor AMD Ryzen 7 1700 Eight-Core Processor, 3300 Mhz, 8 Core(s), 16 Logical Processor(s)

64GB RAM

From my recent experiences with 9.X.X there are a lot of bugs going on, far too many to spend all the time documenting properly.  But most are avoidable or can be worked around with some care and careful recovery use of the .B## & .S## files to get back to somewhere near where the bugs are.

You guys need to develop better unit testing regimes and slow down the pace of change.

My PC is a super heavy recently built workstation and I can't even move a 50mm x 50mm 4 layer board without it taking forever to keep up (making it impossible to do a full move).  I have resigned myself to not doing the move to avoid the issue.

I am just reporting the more obvious problems and errors that are easily repeatable.

Eagle just happened to have crashed while I was doing this again now.

So, even after a full reboot I have retried the issue and can confirm it is still repeatable.

 

Number of Pads: 60

Number of Vias: 805

Number of Smds: 891

Smds in Top: 253

Smds in Bot: 638

Number of holes: 10

Total number of drills: 875

 

Regards, Rod.

0 Likes

jorge_garcia
Autodesk
Autodesk
Hi Rod,

I hope you're doing well. This bug has been confirmed and a bug report created. Stay tuned for a fix shortly.

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

Best Regards,


Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

jeremymeans
Community Visitor
Community Visitor

I can confirm that this bug is still present nearly 5 years later in 2023.

 

It definitely happens when items are moved inside of a group.

0 Likes

anguyenYW4Y3
Explorer
Explorer

this bug still hasn't been fixed...what a joke