Dear OM community,
I have a new bug that was not apparent previously. When I’m setting default values in a subpatch, after pressing apply, the value looks saved. However, the subpatch don’t see the value ‘on the outside, ’even after “updating doc” and saving everything.
Any suggestions?
Thank you
Hello,
I don’t think this is a bug, but certainly an aspect that is not very clear with the system of inputs.
Setting a default value in the input-box editor as you did allows to use this value when the patch is evaluated “from inside” : patches are “closed” objects that are generally not aware of their context (no access to what is entered or connected to the input of the patch box).
This value has no effect outside, at the level of the patch box, where you need to set a value to the input of the box.
This value (even if it is the NIL value) will substitute the default value of the input-box.
I don’t think this is a “new” thing, I believe it always worked like this.
It actually makes sense especially when you are dealing with “blue” (global) abstractions, where a same patch (and therefore, a same input) can be used at several places in other patches, with different input or connected values.
I hope this helps,
Jean
Dear Jean,
Thank you for your answer. I may have not made myself clear. I’m sending you another example taken from 2 abstractions. The one has default values that actually work, the other has default values that do NOT work. I don’t know why the one does work and the other doesn’t but the problem is there. I’m sure this is a new bug because I’m using this feature for ages and now it is inconsistent.
Thank you for your time
I would say that the second example “works” because you probably entered the default value by clicking on the patch box inlets (from its container patch on the left).
… or Are you saying that changing the value in the input windows at the right make it change as well on the box inlets ?
Yes, I’m talking about the second case you are suggesting “changing the value in the input windows at the right make it change as well on the box inlets”. I have entered those values from the input window, inside the patch.
In other words, in previous versions, you could save a default value in the input window, which would affect the patch internally (in case, for example, we needed to test it) AND externally (in case we have set a default value that we don’t need to change it in every instance - where the patch remembers it also when used on the outside).
This is STILL the case with SOME of the patches I’m using. I don’t know why in some cases the feature is active and in others it isn’t. I find it very usefull as for example in MAX you create and object that already has default values that we can change them optionally.
Hi – I 've been able to test with OM 6.5 (the oldest version available on ForumNet)
Here is what I have been able to observe (in both 6.5 and 6.10) : when you insert the patch in the new patch, the value of the inlets of the new created box is set to the one of the input inside. However, once the box is created, further changes on either side are not reflected on the other side. I can’t find a way to make it behave differently (i.e. changing the value of the input inside the patch editor updates the inlet values in corresponding boxes in other patches – if they already exist.). Can you ?