How to hide inputs/outputs of gui elements from control panel

[NaN]

Hi,

when building a subpatch that contains several combo boxes I wondered whether it is possible to hide the input and output slots from the sub patch. This would be very handy as the output of the combo box is only an intermediate value that should not be directly accessible from outside the sub patch.
Another related question: For native modules parameters that can be read and written have in and out slots in the same line (so e.g. for the ComboBox module there are not two "text" lines for in and for out but a single line with both an input and an output). Is that also possible for user subpatches?


Perhaps it's easier to understand with an example.
Essentially I want to build a subpatch with a content like this:

ControllerNumber: Data In ------> SelectCtrlNum : Combobox ----VerifyControllerNumber : Subpatch--> ControllerNumber: Data Out
^ |
| |
-----------------------------------------------------------------------------------------------

where the VerifyControllerNumber subpatch normally just returns the the value it got as input but in some special states some controller numbers are not allowed, so the verifyer module would exchange the controller number with another one that is valid in the current state and update the SelectCtrlNum combobox appropriately.

The input and output slots of such a subpatch would look like that in Usine:

o--ControllerNumber (from Data In)
ControllerNumber (from Combobox Out)-o
ControllerNumber (from Data Out)-o

What I'd like to have is something like that though:
o-ControllerNumber-o

where the input comes from ControllerNumber :Data In and the output from ControllerNumber: Data Out


Is something like that possible with the current Usine version?

Thanks,
NaN

[nay-seven]

have you try the different state of the subpatch by clicking on the white square like this :

for inlet of a combobox , i've also test something : adding a get from bus module will hide the inlet in some case
but in many case , i don't think it's possible..

[NaN]

Hi,

nay-seven, thanks for trying to help!

I already tried the subpatch states, none of the three variants shows the inputs/outputs I'd need. Adding SendBus does not do the trick in my case..
Now I switched to scripting, there I can explicitly use SetIsOutput/SetIsInput in order to get exactly the output configuration that I want.

Now I only have some "cosmetical problems" as I have not managed to add Separators and labels in order to structure and describe my combo boxes in the control panel. Is there a way to add something like separators and labels in the init function of a script? (In the mean time I use local "ptTextfield" parameters with IsInput and IsOuput := false and ReadOnly := true. Unfortunately the "SetReadOnly(myTextField, true);" call does not seem to have any effect, so the downside of this workaround is that the user can click and modify the textfield). Any better ideas?

Thanks,
NaN

[nay-seven]

sorry , don't have work enough with scripts yet...
hope a specialist take a look soon...

[bsork]

AFAIK, there's no other way of adding separators to script other than using dummy parameters, which - if I understand you correctly - you do already.

But I don't really understand why you would want to do that. As long as the parameters are declared in the right order with descriptive names, and SetIsInput/Output is used where appropiate, you should rather use comments/texts in the patch and/or comments within the script to add extra information.

[NaN]

Hi bsork,

thanks for your answer.
I have several combo boxes where you can choose CCs. As looking into the midi spec each time you want to assign a CC is a little bit tedious, I gave them descriptive names. This leads to rather long texts, so in order to match the limited space in the control panel I wanted to ommit the combo box name and place matching labels above the individual combo boxes for better readability.
Will do some more experiments with textfields and getting readonly to work in the evening.

NaN