ParaView 3 Telecon 09/11/2007: Difference between revisions
No edit summary |
No edit summary |
||
| Line 35: | Line 35: | ||
Eric will filter the list of icons Dave T. requested and send Berk a revised list of icons. | Eric will filter the list of icons Dave T. requested and send Berk a revised list of icons. | ||
== Exodus reader refresh == | |||
We have a new-ish request from a user to be able to refresh the exodus reader. This is so that ParaView can look at output files from running simulations and looking at the latest results that were written while the vis session has been going on. | |||
== When are we branching? == | |||
Utkarsh suggests branching in 2 weeks. That does not give us much branch time for bugs, but we can release a beta release of ParaView which we can then release a patch release for the official stable release. | |||
Latest revision as of 12:35, 11 September 2007
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Change meeting day |
| 2 | Moreland | Range information in Exodus Panel |
| 3 | Moreland | Adding extension on state files |
| 4 | Moreland | Icons for Exodus reader |
| 5 | All | Open ParaView 3.2 Bugs |
Range information in Exodus Panel
Ken suggests getting rid of the column in the variable list in the exodus panel. The reasons are:
- This information is just a duplicate of what is in the information panel.
- I have not checked recently, but there have certainly been bugs where the data was out-of-date (i.e. gave the wrong range for the current timestep).
- It is confusing for users to have "Unavailable" next to all the variables when they first start up. I am just responding to a user who was so confused by this he thought ParaView could not read in Exodus variables.
Corey informs us that the range column was put there before the information panel was in place. Thus, the information is probably obsolete. There are no objections, so I will raise a bug report to get rid of it.
Extensions when saving files
Should ParaView automatically add extensions to files that already have extensions? The problem is that any time there is a . in a file, that can be interpreted as an extension, which may not be the case.
Berk has a fancy idea using the same convention as the Mac where you have a checkbox that shows or hides the extension. We can raise a feature request and just assign it a low priority.
Icons for the Exodus reader
Eric will filter the list of icons Dave T. requested and send Berk a revised list of icons.
Exodus reader refresh
We have a new-ish request from a user to be able to refresh the exodus reader. This is so that ParaView can look at output files from running simulations and looking at the latest results that were written while the vis session has been going on.
When are we branching?
Utkarsh suggests branching in 2 weeks. That does not give us much branch time for bugs, but we can release a beta release of ParaView which we can then release a patch release for the official stable release.
