Skip to content

Commit

Permalink
Typo.
Browse files Browse the repository at this point in the history
  • Loading branch information
sletz committed Oct 4, 2024
1 parent c4ce965 commit 0bb0f4d
Show file tree
Hide file tree
Showing 6 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -477,5 +477,5 @@ <h4 class="modal-title" id="keyboardModalLabel">Keyboard Shortcuts</h4>

<!--
MkDocs version : 1.5.3
Build Date UTC : 2024-10-02 15:31:20.122213+00:00
Build Date UTC : 2024-10-04 14:10:37.513172+00:00
-->
2 changes: 1 addition & 1 deletion docs/manual/faq/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -478,7 +478,7 @@ <h2 id="what-is-the-situation-about-faust-compiler-licence-and-the-deployed-code
<p>A: You can freely use Faust to develop commercial software. The GPL license of the compiler <em>doesn't</em> apply to the code generated by the compiler. </p>
<p>The license of the code generated by the Faust compiler depends only on the licenses of the input files. You should therefore check the licenses of the Faust libraries used and the architecture files. On the whole, when used unmodified, Faust libraries and architecture files are compatible with commercial, non-open source use.</p>
<h2 id="surprising-effects-of-vgrouphgroup-on-how-controls-and-parameters-work">Surprising effects of vgroup/hgroup on how controls and parameters work</h2>
<p>User interface widget primitives like <code>button</code>, <code>vslider/hslider</code>, <code>vbargraph/hbargraph</code> allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hiearchical manner using <code>vgroup/hgroup/tgroup</code> primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.</p>
<p>User interface widget primitives like <code>button</code>, <code>vslider/hslider</code>, <code>vbargraph/hbargraph</code> allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hierarchical manner using <code>vgroup/hgroup/tgroup</code> primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.</p>
<p>Widgets that have the <strong>same path</strong> in the hiearchical structure will correspond to a same controller and will appear once in the GUI. For instance the following DSP code does not contain any explicit grouping mechanism:</p>
<pre><code>import(&quot;stdfaust.lib&quot;);

Expand Down
2 changes: 1 addition & 1 deletion docs/search/search_index.json

Large diffs are not rendered by default.

Binary file modified docs/sitemap.xml.gz
Binary file not shown.
2 changes: 1 addition & 1 deletion mkdocs/docs/manual/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ The license of the code generated by the Faust compiler depends only on the lice

## Surprising effects of vgroup/hgroup on how controls and parameters work

User interface widget primitives like `button`, `vslider/hslider`, `vbargraph/hbargraph` allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hiearchical manner using `vgroup/hgroup/tgroup` primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.
User interface widget primitives like `button`, `vslider/hslider`, `vbargraph/hbargraph` allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hierarchical manner using `vgroup/hgroup/tgroup` primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.

Widgets that have the **same path** in the hiearchical structure will correspond to a same controller and will appear once in the GUI. For instance the following DSP code does not contain any explicit grouping mechanism:

Expand Down
2 changes: 1 addition & 1 deletion src/manual/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ The license of the code generated by the Faust compiler depends only on the lice

## Surprising effects of vgroup/hgroup on how controls and parameters work

User interface widget primitives like `button`, `vslider/hslider`, `vbargraph/hbargraph` allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hiearchical manner using `vgroup/hgroup/tgroup` primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.
User interface widget primitives like `button`, `vslider/hslider`, `vbargraph/hbargraph` allow for an abstract description of a user interface from within the Faust code. They can be grouped in a hierarchical manner using `vgroup/hgroup/tgroup` primitives. Each widget then has an associated path name obtained by concatenating the labels of all its surrounding groups with its own label.

Widgets that have the **same path** in the hiearchical structure will correspond to a same controller and will appear once in the GUI. For instance the following DSP code does not contain any explicit grouping mechanism:

Expand Down

0 comments on commit 0bb0f4d

Please sign in to comment.