Hello Dear Developers and Users,
I wanted to get some advice on an issue.
Suppose I am trying to develop a module named A, where one of the inputs of Module A is the output from another module, Module B which has already been developed. In this case, I could develop Module A completely independently. However, this would mean that the user would first need to go to Module B to generate its output, which is required as an input for Module A. Then, user would have to go to Module A and select the output from Module B as one of the inputs before running it.
My question is: for the sake of user convenience, would it be logical to integrate the settings/options of Module B directly into Module A, so that the user doesn’t need to first run Module B and then go to Module A?
Maybe it will be clearer if I explain with an example. In the implementation of Module A, I need the output from the Isodose module, specifically the Number of iso levels and Labels (which seem to be in terms of Dose (Gy) in Iso levels table) which need to be set or adjusted by the user. Can I add these two inputs from the Isodose panel (including number of iso levels and Label (in Gy)) as Spin boxes to the panel of Module A so that when Module A runs, the Isodose module will be executed in the background?
In this regard, I realized that it is possible to access the Isodose module in the Python Interactor using slicer.util.getModule('Isodose'). There is also a method called setProperty. Can I achieve my goal by specifying the arguments of this method?
Best regards.
Shahrokh