<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Unexpected results with DELETE command in scripts in EAGLE Forum (Read-Only)</title>
    <link>https://forums.autodesk.com/t5/eagle-forum-read-only/unexpected-results-with-delete-command-in-scripts/m-p/7254074#M35079</link>
    <description>&lt;P&gt;I have a board with 4 identical sections that are each based on one module in the schematic. I have done the layout and routing for section 1 manually, but to avoid having to constantly adjust the layout of all 4 sections, I wrote a ULP script that:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) attempts to clean up sections 2-4 by&amp;nbsp;ripping up old wires and deleting old polygons&lt;/P&gt;&lt;P&gt;2) copies the wires, vias and polygons from section 1 into the other three sections&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The copy part works well, but I am&amp;nbsp;getting unexpected results with the DELETE commands during the "cleanup" phase of the script. It appears that if -- for some reason -- the object that was supposed to be deleted is no longer at its place when the script runs, the DELETE command will erase whatever other object it finds nearby: parts, dimension lines, air wires, whatever.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the "set" parameter "catch_factor" and thought that setting it to 0 would work, but no (I also tried 1 with no success).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to avoid this "eager" delete behavior?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know of a better way to lay out and route a 4 section board?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Eagle 7.7.0 for Mac.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;doug&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jul 2017 00:41:51 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-07-26T00:41:51Z</dc:date>
    <item>
      <title>Unexpected results with DELETE command in scripts</title>
      <link>https://forums.autodesk.com/t5/eagle-forum-read-only/unexpected-results-with-delete-command-in-scripts/m-p/7254074#M35079</link>
      <description>&lt;P&gt;I have a board with 4 identical sections that are each based on one module in the schematic. I have done the layout and routing for section 1 manually, but to avoid having to constantly adjust the layout of all 4 sections, I wrote a ULP script that:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) attempts to clean up sections 2-4 by&amp;nbsp;ripping up old wires and deleting old polygons&lt;/P&gt;&lt;P&gt;2) copies the wires, vias and polygons from section 1 into the other three sections&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The copy part works well, but I am&amp;nbsp;getting unexpected results with the DELETE commands during the "cleanup" phase of the script. It appears that if -- for some reason -- the object that was supposed to be deleted is no longer at its place when the script runs, the DELETE command will erase whatever other object it finds nearby: parts, dimension lines, air wires, whatever.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the "set" parameter "catch_factor" and thought that setting it to 0 would work, but no (I also tried 1 with no success).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to avoid this "eager" delete behavior?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know of a better way to lay out and route a 4 section board?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Eagle 7.7.0 for Mac.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;doug&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2017 00:41:51 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/eagle-forum-read-only/unexpected-results-with-delete-command-in-scripts/m-p/7254074#M35079</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-07-26T00:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected results with DELETE command in scripts</title>
      <link>https://forums.autodesk.com/t5/eagle-forum-read-only/unexpected-results-with-delete-command-in-scripts/m-p/7261838#M35080</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@Anonymous,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you're having a great day. I apologize for the delay in getting back to you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The DELETE command isn't supposed to be scripted with locations, in that case it's behavior may be unpredictable. The HELP page for the DELETE command doesn't offer any information on using coordinates to specify what to delete from the command line.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of our users wrote a similar ULP a few years ago and it seemed to work pretty well. The big deficiency it had was when dealing with Power signals but other than that it worked really well. This is something we want to address once we get to working on the hierarchy overhaul.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll see if I can get it from him and pass it on to you. Shoot me a direct message with your e-mail and if the user can get the file to me I'll forward it to you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if there's anything else I can do for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2017 16:57:24 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/eagle-forum-read-only/unexpected-results-with-delete-command-in-scripts/m-p/7261838#M35080</guid>
      <dc:creator>jorge_garcia</dc:creator>
      <dc:date>2017-07-28T16:57:24Z</dc:date>
    </item>
  </channel>
</rss>

