info/BezierInfo-2
1
0
Fork 0
mirror of https://github.com/Pomax/BezierInfo-2.git synced 2025-08-30 11:40:27 +02:00
Code Issues Releases Wiki Activity

smaller btc CTA

Browse Source
This commit is contained in:
Pomax
2021-04-09 09:40:50 -07:00
parent 407d2f3c01
commit bb1bf14e75
11 changed files with 189 additions and 148 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
docs/index.html
View File

@@ -38,7 +38,7 @@
<meta property="og:locale" content="en-GB" />
<meta property="og:type" content="article" />
<meta property="og:published_time" content="2013-06-13T12:00:00+00:00" />
<meta property="og:updated_time" content="2021-03-26T00:54:44+00:00" />
<meta property="og:updated_time" content="2021-04-09T16:39:33+00:00" />
<meta property="og:author" content="Mike 'Pomax' Kamermans" />
<meta property="og:section" content="Bézier Curves" />
<meta property="og:tag" content="Bézier Curves" />
@@ -155,10 +155,6 @@
<h2>Donations and sponsorship</h2>
<a class="btcqr" href="bitcoin:3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu?label=Primer%20on%20Bezier%20Curves">
<img src="./images/3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu.PNG" />
</a>
<p>
If this is a resource that you're using for research, as work reference, or even writing your own software, please consider
<a href="https://www.paypal.com/donate/?cmd=_s-xclick&hosted_button_id=3BNHGHZAS3DP6&locale.x=en_CA">donating</a> (any amount helps) or
@@ -171,13 +167,25 @@
sponsoring the site! I am more than happy to work with your finance department on sponsorship invoicing and recognition.
</p>
<h3>Bitcoin donations:</h3>
<p>
If you prefer to donate via Bitcoin, you can donate either directly to
<a class="btclk" href="bitcoin:3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu?label=Primer%20on%20Bezier%20Curves">3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu</a>
or use the QR code on the right, if that's the kind of convenience you prefer =)
</p>
<div class="btcfh">
<div>
<h3>
Bitcoin donations:
</h3>
<p>
If you prefer to donate via Bitcoin, you can donate either directly to
<a class="btclk" href="bitcoin:3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu?label=Primer%20on%20Bezier%20Curves"
>3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu</a
>
or use the QR code on the right, if that's the kind of convenience you prefer =)
</p>
</div>
<div class="btcqr">
<a href="bitcoin:3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu?label=Primer%20on%20Bezier%20Curves">
<img src="./images/3GY1HbQ2cH9V4xBLnRYdEfc42Nd1ZyjLZu.PNG" />
</a>
</div>
</div>
<br style="clear: both;" />
@@ -5886,13 +5894,9 @@ lli = function(line1, line2):
>,<em>C<sub>2.2</sub></em
>).
</li>
<li>
For each pair, check whether their bounding boxes overlap.
<ol>
<li>If their bounding boxes do not overlap, discard the pair, as there is no intersection between this pair of curves.</li>
<li>If there <em>is</em> overlap, rerun all steps for this pair.</li>
</ol>
</li>
<li>For each pair, check whether their bounding boxes overlap.</li>
<li>If their bounding boxes do not overlap, discard the pair, as there is no intersection between this pair of curves.</li>
<li>If there <em>is</em> overlap, rerun all steps for this pair.</li>
<li>
Once the sub-curves we form are so small that they effectively occupy sub-pixel areas, we consider an intersection found, noting that we
might have a cluster of multiple intersections at the sub-pixel level, out of which we pick one to act as "found" <code>t</code> value
@@ -9197,13 +9201,13 @@ for p = 1 to points.length-3 (inclusive):
</p>
<ol>
<li>We start with <code>low=0</code>, <code>mid=0.5</code> and <code>high=1</code></li>
<li>
That'll fail, so we retry with the interval halved: <code>{0, 0.25, 0.5}</code>
<ul>
<li>If that arc's good, we move back up by half distance: <code>{0, 0.375, 0.75}</code>.</li>
<li>However, if the arc was still bad, we move <em>down</em> by half the distance: <code>{0, 0.125, 0.25}</code>.</li>
</ul>
</li>
<li>That'll fail, so we retry with the interval halved: <code>{0, 0.25, 0.5}</code></li>
</ol>
<ul>
<li>If that arc's good, we move back up by half distance: <code>{0, 0.375, 0.75}</code>.</li>
<li>However, if the arc was still bad, we move <em>down</em> by half the distance: <code>{0, 0.125, 0.25}</code>.</li>
</ul>
<ol start="3">
<li>
We keep doing this over and over until we have two arcs, in sequence, of which the first arc is good, and the second arc is bad. When we
find that pair, we've found the boundary between a good approximation and a bad approximation, and we pick the good arc.