On 09/07/2020 16:59, Nicolas Goaziou wrote:
and it simplifies a lot writing functions.
How so?
thank you Michael, for answering Nicolas' question, in a different and
much structured way than I did in my original message.
the formula you provided —I reduced it slightly, hard coding a
Hello,
Mario Frasca writes:
> I think we really need a bug-tracking mechanism, you know?
H...
I had read about the message you've sent again. However, even if we
don't have a bug-tracking mechanism, you can still group messages
related to the same issue in the same thread. It would be
Hi Mario
For such cases I use ~subseq~ to take the running window out of the
complete range ~@I$2..@II$2~:
| date | measure | running avg |
|---+-+-|
| 01-27 | 604 | |
| 01-28 | 314 | |
| 01-29 | 636 | |
| 01-30 | 305 |
I think we really need a bug-tracking mechanism, you know?
see attachment
On 09/07/2020 16:59, Nicolas Goaziou wrote:
Hello,
Mario Frasca writes:
I've been experimenting with associating the empty cell with the value
nil,
Where?
both ways,
What do you mean?
and it simplifies a lot
Hello,
Mario Frasca writes:
> I've been experimenting with associating the empty cell with the value
> nil,
Where?
> both ways,
What do you mean?
> and it simplifies a lot writing functions.
How so?
> also, I've removed the error generation when reading from outside the
> table (instead
Hi people,
I've been experimenting with associating the empty cell with the value
nil, both ways, and it simplifies a lot writing functions. also, I've
removed the error generation when reading from outside the table
(instead of giving up with a user-error, I now get a nil).
it works for
