Pretty weird problem with the Preset Browser ?
-
Oh yeah, sorry I forgot about this one, I have to fix a merge issue. I remember @ustk told me what to do so I'll fix it soon.
-
Done, and it looks like Christoph has merged scriptnode into my develop branch (I didn't know that was possible). Let me know if it works!
-
@d-healey You rock
Yeah, I've seen that scriptnode merge... I wonder if it works now because I've also seen a newer commit that fixes mac compilation...
I don't see @Christoph-Hart scriptnode merge on my fork... My this doesn't reflect? -
@ustk said in Pretty weird problem with the Preset Browser ?:
eah, I've seen that scriptnode merge... I wonder if it works now because I've also seen a newer commit that fixes mac compilation...
Was there a problem with mac compilation ?
Will build and test tomorrow :)
-
The topic is old, but if suddenly someone, like me, is looking for a solution to correctly switch presets with only 2 columns...
If you set 2 columns in the browser settings, then when you switch the next/previous preset, the browser will return to the category column. With three columns (default), the browser correctly displays the selected preset. Possibly a bad solution, but it works. Just reduce the ratio of the first column to zero if you only need to display 2."NumColumns": 3, "ColumnWidthRatio": [ 0.0, 0.5, 0.5 ],