Hidden project settings?

[dgmulf]

It's possible to create project-specific user settings accessible via the Studio I/O panel for a controller script using the DocumentState class, but is it possible to create invisible settings that keep track of the controller state on a project by project basis?

[moss]

Yes, you can use the "hide ()" function on the Setting.

It took me some time to find out that all Settings actually implement Setting, which provides you several additional functions.

[dgmulf]

Thanks!

[Kirkwood West]

settings.png

There must be some other magic way to get hide() to appear on this class. i'm dying to know here lol.

[Dozius]

Just cast it to Setting and it will work. I don't see this inheritance anywhere in the public API though, so I expect this could change/break at any time without notice.

Code: Select all

((Setting)actual_data).hide();

Something to mention. I couldn't find a way to hide the category, so if you have a whole section of hidden parameters the category will still show up.

Also note that when you rebuild your extension, it appears you also need to reload the active project for the document state to be reflected correctly in the I/O panel.

[Kirkwood West]

Just cast it to Setting and it will work. I don't see this inheritance anywhere in the public API though, so I expect this could change/break at any time without notice.

Code: Select all

((Setting)actual_data).hide();

Something to mention. I couldn't find a way to hide the category, so if you have a whole section of hidden parameters the category will still show up.

Also note that when you rebuild your extension, it appears you also need to reload the active project for the document state to be reflected correctly in the I/O panel.

Thanks for the heads up on that.

The whole document state thing is pretty flakey if you start changing the settings around. Many stale items with no way to clear them out. Old documents with stuff like this i tend to copy all the content out of the project and make a new one.

[moss]

Just cast it to Setting and it will work. I don't see this inheritance anywhere in the public API though, so I expect this could change/break at any time without notice.

Code: Select all

((Setting)actual_data).hide();

Something to mention. I couldn't find a way to hide the category, so if you have a whole section of hidden parameters the category will still show up.

Also note that when you rebuild your extension, it appears you also need to reload the active project for the document state to be reflected correctly in the I/O panel.

Thanks for the heads up on that.

The whole document state thing is pretty flakey if you start changing the settings around. Many stale items with no way to clear them out. Old documents with stuff like this i tend to copy all the content out of the project and make a new one.

Yes, I documented all known bugs here: https://github.com/teotigraphix/Framewo ... /issues/73

Feel free to complain to Bitwig as well, so it is not only me

[antic604]

---