time browser default

Brian, I have submitted enhancement request #797041 to our product development team to add an option to prevent the Time Browser from resetting to zero upon re-compute. I suspect part of the reason it does not do this already is because of the possibility of the selected timestep no longer being valid when re-computing. For example say you had used a timestep of 0.5 hours and were looking at timestep 10.5 hours and you recompute the model with the timestep set to 1.0 hours.

I also noticed you mentioned you are seeing this happen when you "change pipes" - can you elaborate on that? If you mean simply clicking on another pipe to see its properties, I cannot reproduce this (the Time Browser retains its time position for me, at least in a sample file).

Brian, I have submitted enhancement request #797041 to our product development team to add an option to prevent the Time Browser from resetting to zero upon re-compute. I suspect part of the reason it does not do this already is because of the possibility of the selected timestep no longer being valid when re-computing. For example say you had used a timestep of 0.5 hours and were looking at timestep 10.5 hours and you recompute the model with the timestep set to 1.0 hours.

I also noticed you mentioned you are seeing this happen when you "change pipes" - can you elaborate on that? If you mean simply clicking on another pipe to see its properties, I cannot reproduce this (the Time Browser retains its time position for me, at least in a sample file).