P_Petrowiek

storing-numbers-in-an-abstraction

I can't think of one, but it's a problem I've run into from time to time 

as well, and probably worth a think-through, for a solution in the future.

I can't think of one, but it's a problem I've run into from time to time 
as well, and probably worth a think-through, for a solution in the future.

it is not the idea of abstractions to store 

do not forget that a patch could call two 

what might be the right solution for you is

that means use [#1 i] and [#2 f] instead of 

arguments can be initialized from inside,

or by giving the abstraction object box s 

you can now that from outside much easier

it is not the idea of abstractions to store 
stuff inside them. 
do not forget that a patch could call two 
instances of the abstraction patcher.

what might be the right solution for you is
adding arguments to your abstractions.
that means use [#1 i] and [#2 f] instead of 
numboxes and connect a loadbang to them.

later when called as abstraction the 
arguments can be initialized from inside,
or by giving the abstraction object box s 
arguments, and can be set by inlets.

when you want to store "last use values"
you can now that from outside much easier
than with numboxes.


The solution, actually, is to store the values at the level above: you 

would need to get the values somehow (pattrstorage?), and then you'd 

Any built in solution would have to do more or less the same thing, but 

The solution, actually, is to store the values at the level above: you 
would need to get the values somehow (pattrstorage?), and then you'd 
restore them when the patcher loads.

Any built in solution would have to do more or less the same thing, but 
transparently.

storing numbers in an abstraction