Previously, I copied and pasted the code into the Python Interactor every time I ran the code to make sure the Python module worked properly within the 3D slicer. This is because if the module does not operate normally, it is impossible to determine whether the Python module extension method is wrong or my code is wrong.
With the help of many people, I was able to complete the custom module I wanted. thank you.
However, there is still some work left to improve the usability of the module. Extensions are essential because events such as mouse and keyboard clicks and modules must be linked.
Therefore, I need a private module extension method for testing.
What part of the document should I refer to?
Specifically, I would like to know if the extension’s private or public mode changes depending on what action is taken when following the module extension guide.
Previously, I copied and pasted the code into the Python Interactor every time I ran the code to make sure the Python module worked properly within the 3D slicer. This is because if the module does not operate normally, it is impossible to determine whether the Python module extension method is wrong or my code is wrong.
When developing your extensions it is useful to enable the developer mode (you can do this in Edit > Application Settings > Developer > Developer Mode). This, by default, creates a new set of buttons for the scripted modules (these are located on each scripted module side panel): Reload, Reload and Test, Edit and Restart Slicer. These are very useful to make your development a little bit more interactive since you can change your code and reload it without (mostly) the need to restart Slicer. The test button will launch the tests located in the Test class of your module.
With the help of many people, I was able to complete the custom module I wanted. thank you.
However, there is still some work left to improve the usability of the module. Extensions are essential because events such as mouse and keyboard clicks and modules must be linked.
Therefore, I need a private module extension method for testing.
What part of the document should I refer to?
There is testing documentation here: Extensions — 3D Slicer documentation. I personally find very useful to have a look at well-established extensions to learn how to do better testing code.
Specifically, I would like to know if the extension’s private or public mode changes depending on what action is taken when following the module extension guide.
To test an extension, you need to specify location(s) where Slicer should look for additional modules.
If the extension is not built: add all source code folders that contain module .py files to “additional module paths” in modules section in application settings.
If you test by adding the path, is it correct to test only on the local side, not to expose the module?
If this is correct then this is the answer I was looking for.
After all the code is complete, I want to remove the security part and release it.
edit:
What’s the ‘Module .py file’ in 3D slicer?
I know that the python file itself functions as a module, but is it different in 3d slicer?
I guess I asked too hastily. I’ll read the doc properly again and come back. I’m sorry