@esaruoho Since you already numbered the abstractions you can use [namecanvas subpatch-$1] to give them individual names. Then you can use a number to [;subpatch-%1 vis 1( to show them. I don't know if there is a way to just open an array via message. If not you can instead put a subpatch into each abstraction that only contains the array and open these with [namecanvas].

@KMETE And how about this: timegate2-demo.pd

@whale-av Indeed!

I mean, it could have been the house.

@Buck At least you didn't burn the house, smashed the computer and moved to a hotel with a brand new laptop to find that out.

@dgbillotte It just stores each mode and respective value inside [text]. You can click on [text define] to see what is happening. When changing mode to retrieve the value and before writing, it searches for the mode in the first column if it is already there and uses the respective line to read or write. Otherwise it uses 0 as value and writes at the end of [text].

@ddw_music Yes, seperating GUI and logic is key!

@lo94 Maybe something like this:

slider_range.pd

@dgbillotte This supports unlimited modes by looking the values up in a [text]:

multi-knob.pd

@lavirgenmarea Here is a simple solution using list-drip from https://forum.pdpatchrepo.info/topic/11122/faster-list-drip-with-list-store-pd-0-48.

[sel] is used to filter the contents. Getting the filtered element is a little bit awkward, but usually the way to go: Send the element down and let [sel] bang it through.

filter-list.pd