private vs public options
Posted: Mon Dec 18, 2017 6:44 pm
Hi,
I've the following scenario I wasn't able to solve in a simple way. I'd like one option to be private (not in the UI) when the module is used in jamovi, but to be public when the module is used in R. Is that possible without creating a dummy ugly option in the UI that nobody is going to use?
More specifically, the module estimates models based on formulas. In jamovi, the formula is composed internally combining dep-variable, covs-variables and factor-variables, thus the "model" variable is private in the R6 class. When the user uses the module in R, it would be nice that s/he can provide the formula directly, as a formula() object. However, to do that I need the "model" option to be public.
How is the best way to go?
I've the following scenario I wasn't able to solve in a simple way. I'd like one option to be private (not in the UI) when the module is used in jamovi, but to be public when the module is used in R. Is that possible without creating a dummy ugly option in the UI that nobody is going to use?
More specifically, the module estimates models based on formulas. In jamovi, the formula is composed internally combining dep-variable, covs-variables and factor-variables, thus the "model" variable is private in the R6 class. When the user uses the module in R, it would be nice that s/he can provide the formula directly, as a formula() object. However, to do that I need the "model" option to be public.
How is the best way to go?