- Load 3d+t Heart
- Change timestep
- Create new Segmentation
- Click on FastMarching3D
- Error message shows an error in Initialize function of the Fastmarching Filter
- Does not happen if timestep is kept 0
If timestep != 0, the m_CurrentTimeStep is changed with SetCurrentTimeStep(t). In this function Initalize() is called without the m_SmoothFilter initialized before. m_SmoothFilter equals nullptr.
I totally forgot to claim the task but I also worked on it *sigh*. Your fix in D346 solves the problem, but I wondered if function initialize() should really be called if the activated() has not been called yet. An alternative would be to have an additional flag "m_activated" or likewise.
What I also wondered (this was the main reason I hesitated with commiting): I am not entirely familiar with that stepper used in the GUI of the fast marching but I wondered if the implementation can also cause problems when dealing with timesteps/timepoints?