Merge pull request #127 from flucoma/dev

[Release] 1.0.2
nix
James Bradbury 4 years ago committed by GitHub
commit 2ca6e583ca
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -89,7 +89,7 @@ strong::incremental buffer writing - sky is the limit::
code:: code::
// start the entry maker, trigging twice a second // start the entry maker, trigging 30 times per second
( (
~ds.clear; ~ds.clear;
{ {
@ -113,13 +113,17 @@ code::
~ds.clear ~ds.clear
:: ::
strong::circular writing::
strong::Circular Writing::
Each time link::Classes/FluidDataSetWr:: is triggered it is like the link::Classes/FluidDataSet#-setPoint:: method so if the identifier does not exist it creates it. If the identifier does it exist then it updates it with the new values. Each time link::Classes/FluidDataSetWr:: is triggered it is like the link::Classes/FluidDataSet#-setPoint:: method so if the identifier does not exist it creates it. If the identifier does it exist then it updates it with the new values.
By looping code::idNumber:: values, we can use a link::Classes/FluidDataSet:: similar to a "circle buffer", always have the most recent code::n:: points in it that we want. By looping code::idNumber:: values, we can use a link::Classes/FluidDataSet:: similar to a "circle buffer", always have the most recent code::n:: points in it that we want.
code:: code::
~ds.clear;
// always have only the most recent 10 points in the buffer // always have only the most recent 10 points in the buffer
( (
{ {
@ -134,6 +138,6 @@ code::
//print regularly to see a specific identifier being overwritten //print regularly to see a specific identifier being overwritten
~ds.print; ~ds.print;
~ds.clear ~ds.clear;
:: ::

Loading…
Cancel
Save