corkcitygamelan

I have a function object with a line~ and various bits of code hanging off it - to create envelopes.

I have attached a preset object to it and I have saved many envelope shapes.

I now decide that all I really need to see while performing are the presets. So, I encapsulate the lot, except for the preset object.

I am testing what I did... and I immediately realize my error: The preset object is not attached to the function object any more - it is attached to an inlet object ... which does NOT understand "preset". Ah, well, I would have thought the inlet should simply just pass on anything it receives to whatever it is connected to ... but then again, I have an idea why the "preset" object could be different from everything else: it is a two-way conversation along a single patch cord, requiring both inlet and outlet functionality - is this thinking correct? See, I generally don't program ...

3) connect a line~ object to the correct output, patched into a send~ (something) object

4) create a few dozen presets (the more presets you create, the more annoyed you are going to be when you are through with this) and verify that they work.

5) encapsulate everything with the exception of the preset object.

expected result: it should work as before ... but after thinking about it, I changed my expectations ......

expected result: the presets should work again

I have a function object with a line~ and various bits of code hanging off it - to create envelopes.
I have attached a preset object to it and I have saved many envelope shapes.

1) create a function object
2) connect a preset object to the input
3) connect a line~ object to the correct output, patched into a send~ (something) object
4) create a few dozen presets (the more presets you create, the more annoyed you are going to be when you are through with this) and verify that they work.
5) encapsulate everything with the exception of the preset object.

expected result: the presets should work again
actual result: they do NOT work


unexpected-behaviour-of-the-function-object-causes-loss-of-data

They work again for me (Max 7, Windows 32).

I've got a modular function/preset combo which I use in a bpacther. That approach might be good for you.

and it does NOT work, unless function and preset are cvonnected via patch cord ... or not at all, but then the preset includes all interface elements.

sorry, I forgot to mention:
I have a Mac, OSX 10.7.5
and it does NOT  work, unless function and preset are cvonnected via patch cord ... or not at all, but then the preset includes all interface elements.


Unexpected behaviour of the "function" object causes loss of data