MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012749ParaView(No Category)public2011-11-27 11:052016-08-12 09:59
ReporterSteve Robbins 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version3.10.1 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typeincorrect functionality
Summary0012749: Paraview VRML reader should not attempt VRML 1.0 files
DescriptionThe VRML loading code in paraview uses VTK's parser class (vtkVRMLImporter), which only handles VMRL 2.0. Paraview, however, will allow the user to open a VRML 1 file which, after parsing, produces a diagnostic message that does not point to the root cause (i.e. loading a VRML 1 file).

Suggest that Paraview disallow loading VRML versions other than 2. See mailing-list discussion http://www.paraview.org/pipermail/paraview/2011-November/023393.html [^]

A comment in vtkVRMLSource::CanReadFile() says:

  // Technically, the header should start with "#VRML V2.0 utf8", but who's
  // to say that new versions will not be forward compatible. Let's not be
  // perscriptive yet. If some future version of VRML is incompatible, we
  // can make this test more strict.
  int valid = (strncmp(header, "#VRML ", 6) == 0);


It's clear that this test should forbid VRML 1. I think it is also now clear that new versions are NOT forward compatible. VRML has been superceded by X3D (http://www.web3d.org/x3d/specifications/x3d/ [^]) which although it does have a VRML encoding (http://www.web3d.org/x3d/specifications/ISO-IEC-19776-X3DEncodings-All-Edition-1/ [^]) the header starts with "#X3D V3.0", not "VRML".
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-11-27 11:05Steve RobbinsNew Issue
2016-08-12 09:59Kitware RobotNote Added: 0038105
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0038105)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.