Notes
(0020436) user3172 2010-04-27 14:05	git hash for resolved: fe77bcc2f6b2b2770443ff7f70e7b401c20a0a5f

(0020437) Ken Moreland (manager) 2010-04-27 14:12	This is already implemented in ParaView. Before attempting to load a file with a reader, ParaView will attempt to call a method called CanReadFile on that reader object. This mechanism is used to determine which reader to use when multiple readers report supporting the same file extension. When no file extension matches, that dialog box that pops up is already culled of any readers that have reported an inability to read the file. The actual list of readers supported by ParaView is much larger. Most of the remaining readers are there because they do not implement a CanReadFile and so therefore ParaView has no way of knowing whether the read will be meaningful. Of those readers that don't support the CanReadFile, most of those are because the file format provides no viable way of determining if the file is of the correct format.

(0020571) Alan Scott (manager) 2010-05-04 19:58	Tested local server, trunk and 3.8.0, Windows and Linux. If there is one file format that is messing up, please write a specific bug.

(0021273) Utkarsh Ayachit (administrator) 2010-07-07 10:10 edited on: 2010-07-07 10:11	Actually, this bug refers to the issue when 2 file readers indeed support and can read the same file. In that case this results in popping up a dialog to the user and allowing him to choose between the 2 (or more) totally working and valid readers. This typically happens when multiple plugins are loaded all that can support reading the same file format. Since this is not a critical feature, no need for the target version to be 3.8.1. The fix will get included in the 3.10 by default.

(0021285) Ken Moreland (manager) 2010-07-07 11:56	For the record, I don't like this feature. The problem is that you can have two readers that both think they can read the data, but one of them is clearly better. In particular, this can happen when you have a basic format that can have multiple conventions or extensions placed on it. The netCDF reader is exemplar for this. NetCDF is not so much a format as a container. There is a fallback netCDF reader that can read in the data as basic arrays. However, often conventions are placed on top of the arrays to give them specific meaning, and other readers are developed that check the convention and respond to these specific interpretations. For files that follow this convention, both the fallback and the specific readers will claim that they can read the file, but you clearly always want the specific one. Previously this was easily solved by ordering the readers in ParaView, but now you get a pointless dialog box every time.

Issue History
Date Modified	Username	Field	Change
2010-04-27 14:01	user3172	New Issue
2010-04-27 14:05	user3172	Target Version	=> 3.8.2
2010-04-27 14:05	user3172	Note Added: 0020436
2010-04-27 14:12	Ken Moreland	Note Added: 0020437
2010-04-27 14:12	Ken Moreland	Status	backlog => @80@
2010-04-27 14:12	Ken Moreland	Resolution	open => no change required
2010-04-27 14:12	Ken Moreland	Assigned To	=> Ken Moreland
2010-05-04 19:58	Alan Scott	Note Added: 0020571
2010-05-04 19:58	Alan Scott	Status	@80@ => closed
2010-06-15 09:44	Utkarsh Ayachit	Target Version	3.8.2 => 3.8.1
2010-07-07 09:55	Utkarsh Ayachit	Fixed in Version	=> Development
2010-07-07 10:10	Utkarsh Ayachit	Note Added: 0021273
2010-07-07 10:11	Utkarsh Ayachit	Note Edited: 0021273
2010-07-07 10:11	Utkarsh Ayachit	Fixed in Version	Development => 3.10
2010-07-07 10:11	Utkarsh Ayachit	Target Version	3.8.1 => 3.10
2010-07-07 10:11	Utkarsh Ayachit	Resolution	no change required => fixed
2010-07-07 11:56	Ken Moreland	Note Added: 0021285
2011-06-16 13:10	Zack Galbreath	Category	Feature Request => Feature

Relationships