The base issue is that when fiducials are added by clicking with the mouse, an unitialised markup is added to the markups list first, then the coordinates are set by a second call. This first triggers the markup added to list event which adds a row to the table in thte GUI with coordinates of 0,0,0, then triggers a point modified event. UpdateRow is called in both cases, but the jump is only triggered when a "select" is made on the row, aka after the new row is added, it's selected (while the point is still at 0,0,0).

Some possible solutions:

• on mouse click to add in the displayable manager, add a fully initialised point to the list of points (this would be cleanest, but check for side effects - Laurent may have been working around it)
• in the onActiveMarkupsNodePointModifiedEvent method on the widget, if jump to slices is clicked, jump; this will mean that if a user is click+drag moving a fiducial and the GUI has the jump optiion clicked, all the slices will jump (this might fix the shift click drag bug, but it would expand the notion of the click in the table to jump slices check box to include jumping slices when fiducials are moved).
• try to set up a conditional event in onActiveMarkupsNodeMarkupAddedEvent to do the jump to slices after the point has been modified (would rather not, but it's an option)

I think the cleanest would be to only jump if the active point is changed because the user clicked on one of the rows in the markups table. When the active point is modified due to any other reason (e.g., when the widget updates itself from the MRML; or when the user clicks on a fiducial in the slice viewer) the "jump" feature should not be activated.

Disabled jumping to new fiducials:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22921

Thanks Nicole, it works well!