Dorian Meid

> I'm struggling to figure out how to present this in a vaguely sane way. We are talking about this one, right?  I thought about a simple approach...

There is another possibility of making this list and maybe module management more intuitive and easier to use. What about a different way of handling module upgrades? We could just...

> 1. With it being defined in the manifest, it could be different across different versions of the module. For simplicity we would use the latest, could that lead to...

> 'it needs to be possible to upgrade and downgrade across id changes' Exactly, that is also what I mean with "cross-module" upgrades. If the module type is changed in...

I'm also against adding something to the variable for display formatting. Also I don't see any GUI solution. I second that a formatting function for use in an expression would...

Something similar is being worked on.

I see that this gives a lot of freedom. I wouldn't have thought of using an expression function but I can see potential benefits over the solution I suggested somewhere...

I'm fine with `oscillate`, LFO is the abbreviation for "low frequency oscillator" and actually it is a well known technical term but you are right, it wouldn't be the first...

> I think it'll be easier to cycle through 0 to 7 every 500ms with something like `oscillate(500, $(custom:max))` I don't think that cycling through discrete values should be done...

> Oof, this is a rabbit hole.. It appears that 'never lock' feature is a bit flawed, and has been for years.. Maybe not at this place, but I think...