Node Implementation not firing a message on button click to oscOutFilter in custom module

Community Usage questions
1

Raspberry Pi 5
Open Stage Control 1.27.1
Running in node

I am trying to determine why a simple button:

mode: tap
id: oblique_get

is not firing a message to oscOutFilter when tapped. I am not seeing any message when logging.
This worked in my windows 10 version. Any ideas?

Edited for brevity.

module.exports = {
    oscOutFilter: function(data) {
	/* DOES NOT GET HERE */
        console.log(data);
       if (address === '/oblique_get') {

        console.log('In Oblique');
        receive('/modal_oblique', { type: 'f', value: 1});
        var obliqueList = this.getObliqueList(); 
        var item = obliqueList[Math.floor(Math.random()*obliqueList.length)];
        receive('/oblique/set', { type: 'i', value: item});
      }
    }
}

Thank you.

2

All button actions need to be handled by custom module.

3

Did you make sure the button has at least one target (either in its target property, or in the server's send option, or as the first argument if using the scripting function send()) ?

4

I did not have that before and it worked in Win 10.

What should be the target properties value to send internal if the widgets id is "oblique_get"

I only want this message to hit the oscOutFilter and I will handle all interactions there and then basically swallow the message

5

Ok, setting target to something like this is getting me somewhere:

address: auto
preArgs: [1,1]
target: 127.0.0.1:8080

if I do not set the preArgs i get warnings.

Thank you, it works again in the new environment.

6

I did not have that before and it worked in Win 10.

I doubt that, there's really nothing that would explain such a difference based on the OS only. A change in the osc server config seems much more likely.

What should be the target properties value to send internal if the widgets id is "oblique_get"

Not sure to understand what you mean, the target doesn't relate to the id in any way.

I only want this message to hit the oscOutFilter and I will handle all interactions there and then basically swallow the message

In that case you could consider using a "fake" target such as "custom:module", as long as the message is stopped in the custom module with an empty return statement. In any case, sending 127.0.0.1:8080 is likely not a good practice if the osc server is listening on port 8080 (which is the default).

The interest of using a fake target is purely aesthetic though, it's just a way to remind you what the widget is meant to do when looking at its properties.

if I do not set the preArgs i get warnings.

There's nothing wrong with empty preArgs, unless something else was set that'd expect preArgs.

7

I got it working again, after your direction. I will change the address to custom:module instead of 127....

I am stopping the message in the custom module.

Thank you.