I know I’ve been away for quite some time (Life just happened ) but I always knew that, at some point, I would have the opportunity to get back on having fun building docs, and here, by the same occasion .
Well, this kind of happened a month ago (or so) when I began to create my very first personal doc since I went AWOL .
At some point, I evidently hit a wall but found a solution which works for that specific doc
So, completely out of curiosity (but also because I still need and want to learn ) I would like to know if I could have done this differently (and maybe in simpler way as I still tend to overcomplicate things where it’s not necessarily needed )
Any idea(s), would be more than appreciated !
I hope I shared this doc correctly (as it has been a while too) and didn’t make mistakes in the sharing options
I also really want to congratulate everyone for the magistral evolution of Coda !!!
Like the very first time I used Coda : The more I use it, the more ideas I get and therefore, the more I want to use it !
Plus, even though “my Coda” is a little bit rusty, I was more than happy to discover that I didn’t forgot that much during the months I was away and was still able to create a doc from scratch without too much trouble ! This, for me, says a lot about how great Coda is !
See how we return List() instead of blank "" within the If() — ListCombine() would eat empty lists but not empty values.
Now that we have our “break points”, let’s collect a list of 2-item lists for each range’s start and end. If it’s a single-item list, both the start and the end are just going to be the same value:
That’s how you break this calculation into logical steps. No need to calculate missing numbers, no need to compare each one with a different one or whatnot. Just left to right, N-th one with the (N-1)-th one. Collect ranges, then format ranges.
FormulaMap() is a formula I actually have a hard time to “re-learn” how to use (correctly) and when. But I’m getting there !
I was pretty certain while building my example doc that I should’ve looked in that direction but I just couldn’t find a way around it…
This is, like always , a way better and prodigiously simpler solution to my initial problem !
Thank you very very very much for taking the time to look at this !
I’m gonna try and implement it to my doc right away !