# Property "active" working as supposed?

**URL:** <https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084>\
**Category:** Cabbage slugs\
**Created:** [11 November 2026 22:03 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084 "2026-11-11T22:03:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![RZorn](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rzorn/32/2611_2.png) [@RZorn](https://forum.cabbageaudio.com/u/RZorn)\
**Post date:** [11 November 2026 22:03 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/1 "2026-11-11T22:03:00Z")

</div>

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
> 
> ```csound
> "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](https://forum.cabbageaudio.com/uploads/short-url/qhgMrDXbvibDak4l3FDMgFArzOJ.csd) (12.5 KB)

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [12 November 2026 09:04 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/2 "2026-11-12T09:04:37Z")

</div>

Thanks for the report @RZorn I will take a look as soon as I can 👍

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [12 November 2026 11:27 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/3 "2026-11-12T11:27:22Z")

</div>

Fix just pushed and new build triggered. It will be available in about 30/40 minutes here: **[3.0.32-beta](https://github.com/rorywalsh/vscabbage/releases/tag/3.0.32-beta)**

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

```csound
 "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. 👍

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

---

<div class="post-metadata">

**Author:** ![RZorn](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rzorn/32/2611_2.png) [@RZorn](https://forum.cabbageaudio.com/u/RZorn)\
**Post date:** [12 November 2026 20:09 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/4 "2026-11-12T20:09:19Z")

</div>

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:
> 
> ```csound
> 
>   
> 
>   
> "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.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [12 November 2026 20:43 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/5 "2026-11-12T20:43:57Z")

</div>

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..

---

<div class="post-metadata">

**Author:** ![RZorn](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rzorn/32/2611_2.png) [@RZorn](https://forum.cabbageaudio.com/u/RZorn)\
**Post date:** [14 November 2026 07:28 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/6 "2026-11-14T07:28:22Z")

</div>

I tried the ‘codesign’ but it did not help… Anyway I would have suspected that if **that** is not working the plugin won’t be loaded at all by REAPER. But it did - just the version behaving as before the update to 3.0.34-beta.

> 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..

You are right, but I had some reason for it I don’t remember anymore.

Now as a next step I deleted all the products from the first export, ~/Library/Audio/Plug-Ins/VST3/TruePingPong.vst3 as well as the folder ~/Library/CabbageAudio/TruePingPong. Then I tried to directly export into ~/Library/Audio/Plug-Ins/VST3. Same in REAPER as before, even though I restarted REAPER once with the plugin deleted, got the error message and after the re-export the load message from REAPER (plus it appears in ‘new’ after all this).

As a last resort I deleted the line referring to TruePingPong from reaper-vstplugins\_arm64.ini. This forced another reload by REAPER, but still the labels are obstructing the clicks on the rotary sliders.

So my final conclusion is that the mechanism which makes the labels inactive does not work when the effect is called as a plugin, but only in the standalone run from Visual Studio Code.

---

<div class="post-metadata">

**Author:** ![RZorn](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rzorn/32/2611_2.png) [@RZorn](https://forum.cabbageaudio.com/u/RZorn)\
**Post date:** [14 November 2026 07:40 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/7 "2026-11-14T07:40:59Z")

</div>

PS: The complete delete made Cabbage recreate /Users/zorn/Library/CabbageAudio/TruePingPong/cabbage (the folder I noticed before having a date before 3.0.34 was released, seemingly not replaced by the export). I checked label.js in the subfolder widgets. I can see some comments referring to ‘active’ and mouse events. So I guess it is the up-to-date version, see attachment.

[label.js.zip](https://forum.cabbageaudio.com/uploads/short-url/rMtyQMef5dhK00F9V8wohLMIWaw.zip) (2.7 KB)

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [14 November 2026 07:59 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/8 "2026-11-14T07:59:13Z")

</div>

Oh I’m sorry, I misread this as an issue with the actual plugin loading in reaper, and not simply the same issue as before with the labels 🤦

I’ll fix this in a bit, I only verified the fix in vscode. My bad.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [14 November 2026 10:12 UTC](https://forum.cabbageaudio.com/t/property-active-working-as-supposed/5084/9 "2026-11-14T10:12:18Z")

</div>

Apologies for this. It was an oversight on my part. When the new build is ready ( **[3.0.41-beta](https://github.com/rorywalsh/vscabbage/releases/tag/3.0.41-beta)** ) you should be able to open and export again to the same location. It should overwrite the previous files and mouse clicks should pass through as they do in the vscode extension.