Jan125
Jan125
I would like to mention that this issue is NOT fixed by #8103, only mitigated. It does not update the attribute to a platform agnostic path.
I'll see if I can understand the option stuff and GUI, and will add a checkbox next to enabling autosaves next. Unsure if I trust myself with adding only keeping...
Thoughts: -Should rearrange format to be yyyy-mm-dd_hh-mm-ss. -Maybe putting these just into a folder structure like projectname.mmp(z).autosaves/yyyy-mm-dd_hh-mm-ss.mmp(z) would make sense?
As mentioned in that commit, exporting with loops is a case that handle differently. Do we want to keep the current behaviour of loops in export not recalculating the state...
I've not noticed any regressions so far.
I have just found an issue where for discrete automation only, it triggers 1 tick too early.
It seems to happen for all interactions except outvalues. This needs a rewrite to instead check if the current position is a node and has an outvalue, and then set...
valueAt now returns the outValue for a node instead on an inValue by default. For future UI usage, a bool toggle has been added to valueAt to return the inValue...