Property "active" working as supposed?

Cabbage slugs
1

In the attached file for most rotary sliders I am using a separate label widget instead of ValueText to get special formatting. I set “active”:false and from the docs

Active

"active": true

Will deactivate a control if false is set (use 0/1 to update from Csound). Controls which are deactivated can still be updated from Csound. Any widget that has its active property set to false will allow all mouse-clicks to pass through it.

I expect that the label widget is ‘transparent’ for mouse clicks. But when I try to move the sliders I have to click outside the boundaries of the label, otherwise the slider will not move.

TruePingPong.csd (12.5 KB)

2

Thanks for the report @RZorn I will take a look as soon as I can :+1:

3

Fix just pushed and new build triggered. It will be available in about 30/40 minutes here: 3.0.32-beta

I did notice something in your test file. Your form has the following channels:

 "channels": [
                { "id": "formChannel", "event": "valueChanged"                               },
                { "id": "MainForm",    "event": "valueChanged", "range": {"increment": 0.01} },
                { "id": "MainForm",    "event": "valueChanged", "range": {"increment": 0.01} }
            ],

This is a little odd, as the form widget doesn’t support these types of events yet. I’m wondering if you picked this up in the docs somewhere, or if it was just an experiment on your part. Regardless, it’s a good reminder that I should add mouse gesture events to the main form. :+1:

[edit] I pushed an update that provides support for proper events in the form widget. Docs will be updated shortly to reflect this.

4

Thanks!

I am now on 3.0.34-beta and it work with the ‘inactive’ labels. It still does not work in REAPER/MacOS as a VST3 yet. Still the old behaviour. But I am not completely sure about the new workflow of VST3 creation. When I use the ‘Export as VST3’ command and then copy the .vst3 to ~/Library/Audio/Plug-Ins/VST3, is this sufficient? Especially after a version upgrade. I also noticed that at ~/Library/CabbageAudio/TruePingPong all files are touched but not the cabbage subdirectory - OK?

I did notice something in your test file. Your form has the following channels:


  

  
 "channels": [
                { "id": "formChannel", "event": "valueChanged"                               },
                { "id": "MainForm",    "event": "valueChanged", "range": {"increment": 0.01} },
                { "id": "MainForm",    "event": "valueChanged", "range": {"increment": 0.01} }
            ],

This is a little odd, as the form widget doesn’t support these types of events yet. I’m wondering if you picked this up in the docs somewhere, or if it was just an experiment on your part.

That seems to be a scary side effect of Codex. I started to have it assist me, and it turned out to be surprisingly efficient, even though csound and Cabbage 3 may not have so much training data. So somehow it may have guessed that these features exist. Still the question why it inserted the events. Unfortunately, I did not run this under git. I can only remember I was prompting it to copy the label trick among the sliders and rearranging them.

But I had a similar moment with the channel HOST_TIME_SIG_DENOM. Even though this was not yet in the docs at that moment, Codex came up with HOST_TIME_SIG_DEN which was wrong but already a close guess.

5

Right, that would explain it. It’s there now anyway. I usually point my AI assistant the documentation website and let it reads the training data from there. It’s quite good for UI stuff at least.

I’m not sure why your plugin is not loaded. That’s a much bigger issue. Did you try codesigning the plugin?

codesign --force --deep --sign - /path/to/YourPlugin.vst3

The vs extension tries to codesign on export by default, but maybe it’s not working for some reason. The only thing that needs signing is the binary itself, none of the resource need touching or signing at all. Can you try that command let me know if the plugin gets seens.

p.s. why do you copy to VST3 after crreation, why not export directly to the vst3 folder? Copying the bundle after creation can be problematic..