<?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 Medium Fit for Thru Holes in UNC Hole Tables in Customization</title>
    <link>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109900#M3195</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Medium fit is only valid and displayed when the hole table is using metric units.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[cid:image001.png@01CE3516.CDC119A0]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tom U.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Apr 2013 15:38:51 GMT</pubDate>
    <dc:creator>TomU</dc:creator>
    <dc:date>2013-04-09T15:38:51Z</dc:date>
    <item>
      <title>Medium Fit for Thru Holes in UNC Hole Tables</title>
      <link>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109899#M3194</link>
      <description>Hi,I have been trying to incorporate all callout notes for ISO and for UNC/UNF into two tables. This includes all of our applicable scenarios: Tapped, Clearance, C'BORE and C'SINK.Did this by adding a DEFAULT_CALLOUT_FORMAT_DATA section to each table and it works brilliantly.The</description>
      <pubDate>Sun, 13 Dec 2020 17:07:26 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109899#M3194</guid>
      <dc:creator>ptc-2513036</dc:creator>
      <dc:date>2020-12-13T17:07:26Z</dc:date>
    </item>
    <item>
      <title>Medium Fit for Thru Holes in UNC Hole Tables</title>
      <link>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109900#M3195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Medium fit is only valid and displayed when the hole table is using metric units.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[cid:image001.png@01CE3516.CDC119A0]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tom U.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2013 15:38:51 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109900#M3195</guid>
      <dc:creator>TomU</dc:creator>
      <dc:date>2013-04-09T15:38:51Z</dc:date>
    </item>
    <item>
      <title>Medium Fit for Thru Holes in UNC Hole Tables</title>
      <link>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109901#M3196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No idea.  Asking ‘why’ about PTC products usually doesn’t lead to a satisfying answer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Why can’t holes change size via relations (1/2-13 to 3/8-16, etc.)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Why can’t holes change size via a family table?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Why can’t thread depth be controlled independently?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Why can’t drill depth be controlled independently?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Why haven’t the hole tables been updated/expanded since version 24 (22 for UNF)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;… and on and on.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It’s no wonder people are forced to create their own custom holes and the tools to use them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tom U.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2013 16:00:33 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Customization/Medium-Fit-for-Thru-Holes-in-UNC-Hole-Tables/m-p/109901#M3196</guid>
      <dc:creator>TomU</dc:creator>
      <dc:date>2013-04-09T16:00:33Z</dc:date>
    </item>
  </channel>
</rss>

