Reader time overrides saved state time
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
I was playing with the ability to save the ParaView state with animation settings. I was loading disk_out_ref, creating an animation, and then saving the state. When I loaded the state, the start and end time got mangled (they were both set to 0).
At first I thought that the start and end times were not being saved, but I tried a different animation with sphere source and it worked just fine. I think what is happening is that because disk_out_ref is an exodus file and the exodus reader has time support, ParaView is getting the time from the exodus reader and then overwriting the values that were loaded from the state file.
My example is a little artificial, but it is not unreasonable for a user to change the start and end times of an animation to limit the animation to some interesting time slice, which I think will be lost under the current implementation.