Extending the Markups module

cpinter · March 4, 2022, 2:26pm

If I understand your question correctly (I think btw it should be a new thread), then I have a simple suggestion.

I recently implemented a similar use case, in which the user clicks a button that says “Add ROI”, but in reality it initiates fiducial placement, which then, by observing the point added event, creates a ROI in the same position as a center. The fiducial node is not used for anything else and I am not interested in seeing it in any list. Is this the same kind of use case?

If so, my solution was just to call HideFromEditorsOn for the fiducials node, and it worked nicely.

RafaelPalomar · March 4, 2022, 2:43pm

Thanks @cpinter. Would HideFromEditorsOn prevent the creation of the markups add button in the toolbar and in the Markups module gui? I have a few of these ephimeral markups and it clutters the UI for something the user should never use independently.

cpinter · March 4, 2022, 3:06pm

I don’t quite understand. Is it a new markup type? Or why is any button created?

RafaelPalomar · March 4, 2022, 3:12pm

In the pluggable architecture, the markups toolbar and the Markups UI get populated with the registered markups. If I register a new markup in an external module a new button for adding a markup of that type is added. I want to avoid having “add markups” buttons for these ephimeral markups, they cannot be used directly and users should not get a button to add something they cannot use. Does it make sense?

cpinter · March 4, 2022, 3:21pm

Ah I see, so it is a new type. I got confused by the register function. Anyway, as I see there is a createPushButton argument in the function

github.com

Slicer/Slicer/blob/master/Modules/Loadable/Markups/Logic/vtkSlicerMarkupsLogic.h#L261

      
        
            vtkMRMLMarkupsJsonStorageNode* AddNewJsonStorageNodeForMarkupsType(std::string markupsType);
            
            
/// Registers a markup and its corresponding widget to be handled by the Markups module.
            /// For a markup to be handled by this module (processed by the displayable
            /// manager, UI and subject hierarchy) it needs to be registered using this method.
            /// The method also registers the markupsNode class in the scene.
            /// \param markupsNode MRMLMarkups node to be registered.
            /// \param markupsWidget vtkSlicerWidget associated to the MRMLMarkups node registered.
            void RegisterMarkupsNode(vtkMRMLMarkupsNode* markupsNode,
                                     vtkSlicerMarkupsWidget* markupsWidget,
                                     bool createPushButton=true);
            
            
/// Unregisters a markup and its corresponding widget. This will trigger the
            /// vtkSlicerMarkupsLogic::MarkupUnregistered event.
            /// \param markupsNode MRMLMakrups node to be unregistered.
            void UnregisterMarkupsNode(vtkMRMLMarkupsNode*  markupsNode);
            
            
/// This returns an instance to a corresponding vtkSlicerMarkupsWidget associated
            /// to the indicated markups name.
            /// \param markupsType registered class to retrieve the associated widget.
            /// \return pointer to associated vtkSLicerMarkupsWidget or nullptr if the MRML node

Unless I misunderstand names again…

RafaelPalomar · March 4, 2022, 3:24pm

Yes, of couse! Thank you @cpinter. The funny thing is that I created that function, but I did not remember about it

Topic		Replies	Views
Markups Module enhancements Development	5	676	October 10, 2018
A user's proposal for Markups Module enhancements Development markups-fiducials , module , markups	20	1576	August 16, 2018
Markups module confusion - suggestions to improve Development	5	405	June 18, 2020
Markups Node Table for vtkMRMLMarkupsLineNode Development	2	436	July 8, 2020
Clone markups node Support	2	233	October 2, 2019

Extending the Markups module

Related Topics