Here's a fun one.
While working on a project I noticed that when I edit a component and click on "drawing" under the installtion code window, I noticed an installation code "EXTRUDER SYSTEM" that is not supposed to be in this drawing (or the project for that matter, we changed that installation to "EXTRUDER_SYS").
When I do a "find replace component text" that installation code is no where to be found by that function.
As a matter of fact, after all components were checked, none contained that installation code ("EXRUDER SYSTEM").
After much puzzling I finally discovered that the signal arrows and the wire numbers associated with them were causing this "EXTRUDER SYSTEM" installation code to be in the drawing.
The attached drawing was WBlocked out of the drawing. One, or more, of the signal arrows is causing the edit component dialogue box to "see" the "EXTRUDER SYSTEM" installation code, even though no components actually have that attribute set to that value.
Signal arrows do not have the "inst" attribute, nor is any Xdata on the signal arrows putting the "inst" attribute on them that way.
Same with wire numbers, once the signal arrows AND the wire numbers are deleted, the "EXTRUDER SYSTEM" goes away.
Try WBlocking the signal arrows out, then bring them back in... the faulty installation code will reappear.
Anyone know how this can even be possible?
Solved! Go to Solution.
Solved by darrell1gregg. Go to Solution.
Your wire number blocks and signal arrows have xdata on them, VIA_WD_INST and VIA_WD_LOC. I don't know why they would or how it got there but that is where it is coming from when you pick the Drawing button when you edit a component.
I don't know of an automatic way to remove this xdata, but you can use the xdata editor provided (AEXDATA) to do it manually.
Regards,
Pat Murnen
well I'll be danged.. I had checked some of the signal arrows but didn't see anything. it's not on all of them.
ran blockswap and that seemed to clean everything up.
Glad the block swap worked. That was quicker than my suggestion to get rid of it.
Regards,
Pat Murnen
Nate wrote me this LISP file whe nI was having problems with XDATA.
Maybe it can help someone else. Worked great for me...