Currently you need to have enabled volume rendering first before you can add an action. Better to have user select a volume and auto-add the start/end/current volume properties automatically.

Also reset volume property to be the target when running the animation.

Make it easier to jump to editing the start or end property and also to detect when the control points don't match (maybe auto correct somehow).

From Murat:

Explain the meaning of target vs start/end volume property in transfer function track.

From Murat:

A button that says ‘export movie’ which will bring the screen capture module with the correct inputs (particularly the sequences input).

From Murat:

Also Sara said perhaps it makes some sense to tie the Animator module with our PC animation tool. (I can’t recall how or why right now, but made sense at the moment. I am sure she will chime in on that).

Want to be sure we can control animation screen size, frame rate, and other settings precisely.

Currently ids are hard coded from the selftest demo, but they should be allocated when added to the script.

From Murat:

If possible, add more than two VP. (Though I am not sure how we can control their placement in the existing user interface.)

This can be provided via class methods at the AnimatorAction level.

Creates a confusion for the user which one is being actually used. Consider adding suffices or not creating a new one nodes Start and End ROI exists.

We could allow fade-in and fade-out of titles, captions, and content. This could be done in 2D, perhaps the most general purpose way would be to use webengine and/or svg for arbitrary content (need to confirm transparent overlay).

From Murat:

Options to make other default rotations possible in rotation track (currently only yaw is present I think).

Currently only the default 5s animation is supported.

Some of the action ui elements aren't fully deleted.

removeRow should work, but doesn't seem to be wrapped.

https://doc.qt.io/qt-5/qformlayout.html#removeRow