Skip to content

Commit 96e09d9

Browse files
Update for 2022.0.1.354 Release
1 parent 42c85d0 commit 96e09d9

File tree

3 files changed

+34
-12
lines changed

3 files changed

+34
-12
lines changed

Sketchup/ComponentDefinition.html

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -789,7 +789,7 @@ <h2>
789789

790790

791791
<span class="summary_desc"><div class='inline'>
792-
<p>The name= method is used to set the name of the component definition.</p>
792+
<p>The <span class='object_link'><a href="#name=-instance_method" title="Sketchup::ComponentDefinition#name= (method)">#name=</a></span> method is used to set the name of the component definition.</p>
793793
</div></span>
794794

795795
</li>
@@ -2783,7 +2783,9 @@ <h3 class="signature " id="name=-instance_method">
27832783
</h3><div class="docstring">
27842784
<div class="discussion">
27852785

2786-
<p>The name= method is used to set the name of the component definition.</p>
2786+
<p>The <span class='object_link'><a href="#name=-instance_method" title="Sketchup::ComponentDefinition#name= (method)">#name=</a></span> method is used to set the name of the component definition.</p>
2787+
2788+
<p>The name should be unique to the model, if it&#39;s not the name will automatically be made unique.</p>
27872789

27882790

27892791
</div>
@@ -2828,11 +2830,6 @@ <h3 class="signature " id="name=-instance_method">
28282830

28292831

28302832

2831-
&mdash;
2832-
<div class='inline'>
2833-
<p>the name assigned to the component definition if successful</p>
2834-
</div>
2835-
28362833
</li>
28372834

28382835
</ul>
@@ -2851,6 +2848,22 @@ <h3 class="signature " id="name=-instance_method">
28512848

28522849
</li>
28532850

2851+
</ul>
2852+
<p class="tag_title">Known Bugs:</p>
2853+
<ul class="bug">
2854+
2855+
<li>
2856+
2857+
2858+
2859+
2860+
2861+
<div class='inline'>
2862+
<p>In SketchUp 2022.0 a bug might lead to an available name being incorrectly renamed. Or a name that should be unavailable would be duplicated. This was fixed in SketchUp 2022.0.1.</p>
2863+
</div>
2864+
2865+
</li>
2866+
28542867
</ul>
28552868

28562869
</div>

file.ReleaseNotes.html

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,8 @@ <h2 id="label-Build+Numbers">Build Numbers</h2>
169169

170170
<p>Here are the build numbers for recent SketchUp releases. Note that build numbers in languages besides English are larger for each release, so it is best to check for builds that are greater than or equal to the numbers here.</p>
171171
<ul><li>
172+
<p><strong>SU2022.0.1</strong> = 22.0.354 on Windows 64-bit, 22.0.353 on Mac 64-bit.</p>
173+
</li><li>
172174
<p><strong>SU2022.0</strong> = 22.0.316 on Windows 64-bit, 22.0.315 on Mac 64-bit.</p>
173175
</li><li>
174176
<p><strong>SU2021.1.2</strong> = 21.1.332 on Windows 64-bit, 21.1.331 on Mac 64-bit. (Contained no Ruby API changes)</p>
@@ -238,6 +240,13 @@ <h2 id="label-Build+Numbers">Build Numbers</h2>
238240
<p><strong>SU6 M6</strong> = 6.4.265 on Windows, 6.4.263 on Mac.</p>
239241
</li></ul>
240242

243+
<h1 id="label-What-27s+new+in+SketchUp+2022.0.1">What&#39;s new in SketchUp 2022.0.1</h1>
244+
245+
<h2 id="label-Ruby+API+Bug+Fixes">Ruby API Bug Fixes</h2>
246+
<ul><li>
247+
<p>In SketchUp 2022.0 a bug might lead to an available name being incorrectly renamed. Or a name that should be unavailable would be duplicated. This was fixed in SketchUp 2022.0.1.</p>
248+
</li></ul>
249+
241250
<h1 id="label-What-27s+new+in+SketchUp+2022.0">What&#39;s new in SketchUp 2022.0</h1>
242251

243252
<h2 id="label-EntitiesBuilder">EntitiesBuilder</h2>

file.generating_geometry.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -392,8 +392,8 @@ <h4 id="label-Optimizing+and+keeping+Ruby+objects+alive">Optimizing and keeping
392392

393393
<p>If you are generating geometry from an internal geometry representation you might have code that looks something like this:</p>
394394

395-
<pre class="code cpp"><code class="cpp"><span class="cp">#include &lt;algorithm&gt;
396-
#include &lt;vector&gt;
395+
<pre class="code cpp"><code class="cpp"><span class="cp">#include</span> <span class="cpf">&lt;algorithm&gt;</span><span class="cp">
396+
#include</span> <span class="cpf">&lt;vector&gt;</span><span class="cp">
397397
</span>
398398
<span class="kt">void</span> <span class="nf">generate</span><span class="p">(</span><span class="n">std</span><span class="o">::</span><span class="n">vector</span><span class="o">&lt;</span><span class="n">Face</span><span class="o">*&gt;</span> <span class="n">faces</span><span class="p">)</span>
399399
<span class="p">{</span>
@@ -411,9 +411,9 @@ <h4 id="label-Optimizing+and+keeping+Ruby+objects+alive">Optimizing and keeping
411411

412412
<p>Similar to the optimization maximization described for <span class='object_link'><a href="Sketchup/EntitiesBuilder.html" title="Sketchup::EntitiesBuilder (class)">Sketchup::EntitiesBuilder</a></span> you might find that avoiding unnecessarily creating new Ruby objects can yield some performance benefits. Below is an example of one way of doing that:</p>
413413

414-
<pre class="code cpp"><code class="cpp"><span class="cp">#include &lt;algorithm&gt;
415-
#include &lt;unordered_map&gt;
416-
#include &lt;vector&gt;
414+
<pre class="code cpp"><code class="cpp"><span class="cp">#include</span> <span class="cpf">&lt;algorithm&gt;</span><span class="cp">
415+
#include</span> <span class="cpf">&lt;unordered_map&gt;</span><span class="cp">
416+
#include</span> <span class="cpf">&lt;vector&gt;</span><span class="cp">
417417
</span>
418418
<span class="kt">void</span> <span class="nf">generate</span><span class="p">(</span><span class="n">std</span><span class="o">::</span><span class="n">vector</span><span class="o">&lt;</span><span class="n">Face</span><span class="o">*&gt;</span> <span class="n">faces</span><span class="p">)</span>
419419
<span class="p">{</span>

0 commit comments

Comments
 (0)