Notes |
|
(0010184)
|
Utkarsh Ayachit
|
2008-01-18 09:49
|
|
The following patch fixes this issue.
/cvsroot/ParaView3/ParaView3/Qt/Core/pqPipelineRepresentation.cxx,v <-- pqPipelineRepresentation.cxx
new revision: 1.19; previous revision: 1.18 |
|
|
(0010263)
|
Alan Scott
|
2008-01-23 16:22
|
|
Client (XP) Server (6 processors). Trunk, January 23rd.
I still see this issue. Ken has a BIG dataset that he says is unlimited release that we can send out. I am using that. Ask Ken or me for it if necessary.
I bring up this file, and it has a time of 0, time step of 0. In the Information tab, we have Time Index = 0, Value = 30.8525, Index 1 = 31.1025, etc..
I click the Next Frame button, and the time button sets to time step 0 - i.e., 30.8525, time step 0. I click the Next Frame button, now we are (correctly) at 31.1025, time step 1. |
|
|
(0010749)
|
Berk Geveci
|
2008-03-07 08:09
|
|
Utkarsh:
Can you check this out?
Alan:
What is that big dataset you are referring to? Do we have it? |
|
|
(0011335)
|
Ken Moreland
|
2008-04-15 12:29
|
|
The data set Alan is talking about is a semi-large fire data set I sent Berk a while ago.
To make things easier, I attached a simple, small data set that displays the problem. It is a simple modification of the singleSphereAnimation data set in ParaViewData with the time range offset to 10-20. |
|
|
(0011345)
|
Utkarsh Ayachit
|
2008-04-15 15:23
|
|
When a file is opened, if the current time (both the
application time maintained by the time keeper, as well as the animation time
maintained by the animation scene) is not within the range of time values
provided by the while, then we change the current time to be the minimum time
provided by the reader.
/cvsroot/ParaView3/ParaView3/Qt/Core/pqAnimationScene.cxx,v <-- Qt/Core/pqAnimationScene.cxx
new revision: 1.24; previous revision: 1.23
/cvsroot/ParaView3/ParaView3/Qt/Core/pqTimeKeeper.cxx,v <-- Qt/Core/pqTimeKeeper.cxx
new revision: 1.14; previous revision: 1.13 |
|
|
(0011405)
|
Alan Scott
|
2008-04-16 17:15
|
|
|