Problem with a large exported patch seems to be altering something. #696
Replies: 2 comments
-
Since this is an exported patch, I was able to export un-minified and probe the |
Beta Was this translation helpful? Give feedback.
-
ok , found my bug.... it was because I was using Actually, I ended up skipping the entry called Ops.Patch.PL3eri4.CustomObjectValuesAsArray = function()
{
CABLES.Op.apply(this,arguments);
const op=this;
const attachments=op.attachments={};
const
inObj = op.inObject("Object"),
outValues = op.outArray("Values"),
outNumValues = op.outNumber("Num values");
inObj.onChange = () =>
{
const sourceObj = inObj.get();
if (!sourceObj)
{
outNumValues.set(0);
outValues.set([]);
return;
}
const values = Object.entries(sourceObj)
.filter(([key]) => { return key !== "pickedID"; })
.sort(([keyA], [keyB]) => { return keyA.localeCompare(keyB); })
.map(([key, value]) => { return value; });
outNumValues.set(values.length);
outValues.set(values);
};
}; |
Beta Was this translation helpful? Give feedback.
-
OK, sorry for this one - but its difficult to demonstrate because of deep context. I might be able to program something that demonstrates it in a simple way, but that's time consuming at this point. Nevertheless, I will start a thread in case its something obvious.
In this screen grab of the UI running inside Cables editor, we see that the computed scalar that renders a minimap of the parameters, reflects the position of the sliders just fine. It correctly reflects the order of the sidebar in other words.
But the exact same patch exported and rendered from external code, gets the order messed up. Like, upside down?
I can't do much about it, because it is a difference in the Cables export patch which is very difficult for me to navigate out of the editor .
Here is a shot of the same UI , getting the wrong order of transformations, when embedded.
The minimap is drawn like this
Beta Was this translation helpful? Give feedback.
All reactions