Should be fixed now
Modal Filter Bank Efficiency
I got it, itās a working build. I havenāt tested the range sliders yetā¦ but immediately Iām seeing a difference in rendering/parsing behavior on imported widgets, and it makes me a little nervous for what other differences in subtleties might be lurking belowā¦
Hereās an example:
And after:
Iām going to take a look, and it might be an easy fix for thoseā¦ but not sure why they changed, but not ALL of my widgets changed.
Also a minor concern, for some reason the once I install a new drop, I canāt reinstall an older drop without nuking the folder first.
I canāt think of what changes caused that problem? The only change I made was to allow widget that support multiple channels? Hmmm. Strange. If you can narrow it down that would be great.
Ok, good news on both fronts. Range widgets appear to be working in my first tests. Itās great to have those back!
With regards to the āwhite widgetsā, the difference between once that work and the ones that donāt:
Working:
$CONTAINER bounds(0, 0, 25, 10)
{
Not working:
$CONTAINER bounds(0, 0, 25, 10) {
Both rely on the same define of from an external imported file:
#define CONTAINER image colour(0,0,0,0)
Itās an easy fix on my part, so I can easily change it outā¦ but I do want to make sure itās on your radar, because it might have changed some other parsing that we havenāt discovered yet.
For clarity, these are both imported xml sets of widgets, and those are the first lines of the cabbagecode sections
I should have known it was something to do with a macro. Why did I ever introduce these to Cabbage
Because theyāre AWESOME?
Let me test without the macro just for funā¦
Ok, without the macro it appears to break in a new way. The color appears normal, but now the bounds are wrongā¦ I changed the widget that contains the small OL label and square āledā. They used to appear above the āNo Panā knob in the In/Out section. No it appears they have pos(0,0):
FAKE NEWS! my bad. I accidentally pasted over the macro name, but the $ still remained. Itās now working as expected when not using a macro.
So itās a macro issue. Of course it is?!
And a pretty minor one, I donāt mind working around it.
Whatās interesting tho, is it looks like it also solves my problem to just have the colour(x,x,x,x) statement redone after the macro and bounds tooā¦ like so
$CONTAINER bounds(0, 0, 120, 55), colour(0,0,0,0) {
^ I know this because I had worked around this once in the past, so some widgets already had that done to prevent this from happening! Thatās partly why not all of them broke.