Open Inventor - Fixed bugs

Open Inventor Fixed Bugs

Open Inventor 4.0

Patch 4.0.6: Bugs fixed as of January 20, 2003

(#300) SoRayPickAction failed on a strongly zoomed scene. Fixed in a previous patch but not documented.
(#391) SoToVRML2Action changed the input scene graph if the input scene graph contained a vertex property node. [P6]
(#435) The SoMPEGFrameRenderer class did not always record the complete animation. Fixed in a previous patch but not documented.
(#457) Opaque objects became transparent when smooth antialiasing and ADD transparency were enabled. [P6]
(#491) SoQtFullViewer::setClientPopupMenu didn't allow you to define a custom popup menu. The only way to set a custom menu was to change SoQtFullViewer::mainPopup directly. [P6]
(#492) If a Qt viewer was created without any standard popup, the program crashed. [P6]
(#513) QtLargeModelViewer needed various minor cosmetic tweaks to the user interface. [P6]
(#549) The mouseMotion events were never sent to the event callback of the Qt viewers. [P6]
(#606) QtLargeModelViewer adaptative viewing problem. The toggle "Do full rendering when still" had no effect on the display (the image remains simplified when still). In addition when you closed and reopened the "Adaptive Viewing" dialog, the choice on this toggle was lost. [P6]
(#656) Improved performance on interlaced stereo. Fixed in a previous patch but not documented.
(#694) Method SoPNGImageRW::loadPNG sometimes crashed. This bug was introduced in OIV405. [P6]
(#696) (Same as 711) Texture loading failed. The texture bitmap files couldn't be opened. This bug was introduced in OIV405. [P6]
(#697) SoToVRML2Action appeared to modify the width of the displayed lines if the input scene graph contained a vertex property node and if antialiasing was enabled. In fact, part of the OpenGL state was getting lost; the lines appeared wider due to the effects of smoothing and antialiasing. [P6]
(#698) The ELLIPSE lasso type of SoExtSelection wasn't correctly drawn in an non-square viewer. [P6]
(#702) The SoOffscreenRenderer::writeToBMP method produced empty images if a big viewport was used. This bug was introduced in OIV405. [P6]
(#704) The transformBoxDragger couldn't be resized if it was centered on (0.,0.,0.). The error message was: "Inventor error in SbLine::setValue(): Invalid line - direction vector has zero length"
[P6]
(#711) (Same as 696) Texture loading failed. The texture bitmap files couldn't be opened. This bug was introduced in OIV405.[P6]
(#713) InvQt405D.dll was linked with the non-debug version of Qt even though the debug version was available. Now InvQt40xD.dll will be linked against qt-mtxxxD if it is available. Otherwise it will be linked against qt-mtxxx. [P6]
(#715) It was not possible to use an absolute path in an SoImage node. This bug was introduced in OIV405. [P6]
(#716) ivfix incorrectly weeded out a material node during the process of simplifying the scene graph. [P6]
(#719) Calculated normals were sent to OpenGL for SoIndexedTriangleStripSet shapes that had normals, texture coordinates, and materials specified per vertex. The supplied normals (rather than the calculated normals) should have been used. [P6]
(#720) SoSelection failed when selecting lines with a large zoom and an orthographic camera. [P6]
(#721) For a large viewport (3000,1000), the BigImageRender example produced erroneous output. [P6]

Patch 4.0.5: Bugs fixed as of November 10, 2003

(#272) MPEG output had quality defects (moire effects and blocky output) even when the highest output quality was requested (setBitPerSec set to -1 and setCompressionRate set to 0). [P5]
(#373) SoMPEGFrameRenderer::recordFrame consumed a large amount of memory in a multi-thread environment. [P5]
(#538) SoBigImageRenderer did not render a scene with PoSceneView correctly. [P5]
(#602) [Win32] The QtLargeModelViewer project file (.dsp) wasn't provided in the OIV 4.0 distributions. The file was missing from the directory %OIVHOME%\src\Inventor\examples\Qt\QtLargeModelViewer.

By default, the project for VC 6.0 is set up to use Qt 3.1.1. The projects for VC 7.0 and VC 7.1 are set up to use Qt 3.1.2. You may need to change them to use the version of Qt that you have installed on your system. [P5]
(#603) The SoOffscreenRenderer::writeToBMP images didn't precisely match the requested dimensions. [P5]
(#617) The toggleCameraType method was broken in SoXtViewer, SoQtViewer, and SoWinViewer. When the toggleCamera button was pressed on the viewer, the program crashed. Once that was fixed, it was found that if the camera wasn't in a nodeKit, the camera was never set. [P5]
(#639) The same windingType parameter was defined in SoShapeHintsElement and SoGLShapeHintsElement headers. A warning message was generated (at least on Solaris) during compilation:

SoGLShapeHintsElement.h", line 79: Warning windingType hides SoShapeHintsElement::windingType.

[P5]
(#642) SoSwitch caused SoSearchAction to return duplicate paths. If you did this:
```
  SoSearchAction sa;
  sa.setNode( pNode );
  sa.setInterest( SoSearchAction::ALL );
  sa.setSearchingAll( TRUE );
```
and pNode is an SoSwitch, the SoSearchAction would return two identical paths for every instance of the node. [P5]
(#645) The application crashed when using octree ordering and interacting with embedded draggers. [P5]
(#657) SoVRMLSound didn't work in OIV 4.0.4. [P5]
(#660) If an SoTexture2's filename or VRMLImageTexture's url was file://c:etc, the file could not be found. For example, if the url was file://c:/globe.rgb, the program couldn't find the image file. If the url was c:/globe.rgb, the file could be found. [P5]
(#661) MPEGRenderer crashed when several movies were built. The crash didn't occur in one of the SoMPEGRenderer methods but later in the method SoWinRenderArea::render because of a ref count problem. [P5]
(#663) [Win32] The SoWin::threadInit methods call SoInteraction::init, but not SoInteraction::threadInit. Meaning that multi-thread setup for draggers and manipulators was not being done. [P5]
(#664) SoQt was missing its threadInit methods. [P5]
(#667) There was a symbol conflict between INV400.LIB and MSVCRT.LIB when using VC7.1. Both libraries had the symbol (??_M@YGXPAXIHP6EX0@Z@Z). This forced the link order to become important. The problem may be due to using STL. The problem does not occur with the Mentor examples. [P5]
(#671) The IVF AppWizard for VC 7.1 didn't work. When attempting to create a new project, the error was:

"Object with program ID VsWizard.VsWizardEngine cannot be created."

Several Wizard files were updated. See the release notes for information on copying the updated files to the correct location in your VC++ 7.1 installation. [P5]

Patch 4.0.4: Bugs fixed as of September 24, 2003

(#539) SoXtGLWidget did not allow the user application to get control before a redraw triggered by an expose event. exposeCB now calls the new methods onExpose and onOverlayExpose. These methods are protected and virtual, which allows them to be overridden in a custom viewer subclass. [P4]
(#550) (SGI) Switching between OpenGL (raw) stereo and mono viewing on SGI caused the scene to disappear if OIV_NO_OVERLAYS was set. [P4]
(#566) (Linux) Open Inventor did not clear overlays using NVIDIA cards on Linux because the wrong value for the transparent pixel was being used. [P4]
(#591) (SoQt) SoEventCallback returned an invalid button number when mouse buttons 2 and 3 were pressed. [P4]
(#595) When using addFunctionKeyBinding to do camera translation, the initial location was not initialized, which caused the scene to disappear unexpectedly. This behavior could be seen using the SetKeyBinding example in the Features directory. [P4]
(#598) (SGI) The StereoDialog "raw" (OpenGL) stereo choice was sometimes incorrectly grayed out on SGI. [P4]
(#599) Duplicate of 595. [P4]
(#600) New feature: SoViewingReverseDolly, derived from SoViewingFunction, works like SoViewingDolly, but opposite. That is, mouse move up corresponds to "zoom-in" and mouse move down corresponds to "zoom-out". [P4]
(#609) During an SoCallbackAction traversal, if a Material node set the transparency to a non-zero value, subsequent Material nodes could not set transparency (in the state) back to zero. [P4]
(#635) Picking an invisible NURBS curve caused the application to abort. [P4]
(#638) Uninitialized variable in SoGLLazyElement (internal) caused opaque objects to be transparent. [P4]

Bugs fixed in patches 1, 2, and 3

(#447) Fast and Best interlaced stereo modes gave very slow performance on NVIDIA boards.
(#466) SoExtSelection failed in VISIBLE_SHAPES mode and with non-convex lasso. Shapes could be selected by the SoExtSelection even if they were not surrounded by the lasso. It only occurred if the lasso mode was set to VISIBLE_SHAPES.
(#469) On some systems, the SoVRMLSound node caused the application to crash.
(#477) The viewer decorations were drawn incorrectly if the SoQtExaminerViewer (or other viewer) was built with SoQtFullViewer::BuildFlag::BUILD_POPUP (which means to display the viewer without decorations initially).
(#479) Backslashes couldn't be used in Inventor/VRML files in filename specifications. (There was no problem using backslashes in file names specified programmatically.)
(#483) The TreeView demo program didn't find texture/image files that were specifed in files that were drag and dropped. (Files that were opened viaFile->Open worked fine.)
(#487) Setting Anaglyph stereo changed the background color. For example, if the Anaglyph stereo color is red-cyan and the background color is yellow, the background turned red because the glClear was called after the colorMask had been set to red and alpha only.
(#489) The background color showed through at the top of the stereo property sliders.
(#490) SoQt: After a window was made full screen, when it was made NOT full screen, the window contents were not resized and the decorations were lost.
(#496) Duplicate of #514.
(#514) There was a 16-byte memory leak in all elements derived from SoReplacedTextureElement (internal). This leak could potentially affect any action that could be applied to a scene containing a texture and any shape to which a texture could be applied. Although the leak was small, it could occur often enough to cause a problem.
(#517) SoCollisionManager was displaying significantly different collision results for release and debug builds. The release results were incorrect.
(#520) SoCollisionManager had a memory leak. The ref count of certain objects went up each time the Collision Manager was created, and it didn't go down when the Collision Manager was destroyed.
(#527) Using SoQt, in an eventCB of type SoKeyboardEvent, when a keyboard key was held down (auto-repeat), the callback function was called with a sequence of both keydown and keyup events. This is normal behavior for Qt, but Open Inventor programs expect a single keyup event when the key is released.
(#528) OGLInfoUnix.cxx always reported that a direct connection was available.
(#529) SoXtColorEditor.h could not be included on MS-Windows. The compilation failed because it was unable to open <Xm/Xm.h>.
(#530) 2D text in SoBigImageRenderer was incorrect for all but the first tile.
(#534) The SoVRMLBackground node was not passed through SoToVRML2Action. If your initial scene graph contained an SoVRMLBackground node, and you converted the scene graph to VRML2 using SoToVRML2Action, the VRMLBackground node was lost in the conversion process. The error message was: ERROR: Do not know how to treat the class VRMLBackground. The node will be lost in the output.
(#540) Memory leak in SoToVRML2Action. When a big shape (SoTriangleStripSet) was exported to VRML2, there was a (big) memory leak. There was no memory leak in SoToVRMLAction.
(#544) TIFF import didn't correctly load the RGB components on big endian machines.
(#546) SoMarkerSet didn't work with SoOffscreenRenderer. Only one marker was displayed.
(#549) Using SoQt, mouseMove events were only sent to the viewer event callback while a mouse button was pressed. This is normal behavior for Qt, but Open Inventor programs expect to get mouseMove events whenever the cursor is in the Open Inventor window.
(#551) The method SoPreferences::getBool returned the opposite of the value set by setBool.
(#559) The SoVRMLMovieTexture node did not know how to deal with relative paths. If you did a readFile using a relative path name, and the file contained an SoVRMLMovieTexture, the movie texture file was not found.
(#574) SoExtSelection crashed when the rectangle lasso was enabled on Qt viewers.
(#581) There was a problem with caching and transparency. An object was incorrectly rendered as opaque after switching between various draw styles (hidden line, wireframe, etc.)
(#582) After an object's attributes (transparent, opaque) were changed several times, the object was not drawn with the correct transparency. This problem was related to caching. If an object was cached while it was opaque and then its transparency changed, (and rendered delayed), the cache should have been broken but wasn't. If you turned off render caching, problem went away. Note: Although superficially this bug resembles #581, it is different.
(#588) Draggers behaved badly when coordinates in scene were very large. This could be seen when adding a light (e.g., using SceneViewer) to a scene with very large coordinates. The light manipulator behaved erratically.

OFFICIAL RELEASE: Bugs fixed as of April 8, 2003

(#5) If an .iv file already contained VMRL2 nodes, they were lost when the file was converted to VRML2 format. Now they pass through the conversion process unchanged.
(#7) (Enhancement) You couldn't query the current stereo mode using the SoViewVolumeElement. Use this method defined in SoStereoElement: const static SoCamera::StereoMode getStereoMode(SoState *state);
(#25) VRML ROUTEs were not processed if they occurred inside of a node definition.
(#33) SoCollisionManager problems fixed. Crash in SoCollisionManager constructor on large scene (30x24x12 cubes). Also, bad initialization of the transformation in SoCollisionManager after collision.
(#44) (HP using OpenGL) The SoOffscreenRenderer writeToJPEG and writeToPostScript methods used to output black images if multipass antialiasing and/or sorted transparency was ON.
(#65) [UNIX] The visual selection code never asked for stencil buffers.
(#67) A textured NURBS Surface couldn't be selected (the selection and pickFilter callbacks were never called).
(#103) The SoOffscreenRenderer::render method crashed on Linux Redhat 7.1.
(#114) [UNIX] If you closed and reopened the stereo preferences dialog, it didn't remember the previously requested stereo type.
(#119) (NuTCRACKER) Open Inventor didn't correctly handle spaces in the env var SO_DRAGGER_DIR.
(#122) (Solaris) Raw stereo item appeared to be selected initially, but you had to re-select it after enabling stereo for it to take effect.
(#124) (IVF) Exiting an IVF app after pasting from the clipboard caused a debug error "Child Index -1 out of range".
(#128) Deleting all instances of a PROTO or EXTERNPROTO caused their definitions to be deleted. An application would no longer be able to use those definitions.
(#130) The SoTexture2 node was not converted to VRML2 by SoToVRML2Action.
(#131) (IVF) When an Inline node was added to the pending queue, it was ref'ed but not unrefed when taken out of the queue. This caused a memory leak.
(#132) (Win32) The Manual mode of the Material Editor did not update the display. If the Update Frequency of the SoWinMaterialEditor class was set to SoWinMaterialEditor::AFTER_ACCEPT, the display wasn't updated by pressing the Accept button.
(#150) Help button in viewers used to look for Inventor.hlp, which is no longer delivered. Now it looks for RefMan.chm.
(#152) The BLEND mode of texture nodes didn't support images having more than 2 components.
(#158) The SoCollisionManager didn't trigger its collision callback if the transformation was of type SoTransformManip and if its fields were modified by hand.
(#164) The method SoMPEGNavRenderer::setSceneGraph didn't work. The SoMPEGNavRenderer::record method failed (nothing was recorded) on a scene set by the setSceneGraph method. The record method worked on the same scene if the scene was used as parameter of the SoMPEGNavRenderer constructor.
(#172) The SbViewVolume::projectPointToLine method didn't correctly map a 2D point to a 3D line in a non-square window.
(#178) A subtexture applied to a texture that is not a power of 2 was displayed incorrectly.
(#186) SoOctreeOrdering did not return the correct bounding box. The consequence was that the octree was cut by the near and far planes when drawn.
(#188) The SoExtTexture2 node wasn't converted into VRML or VRML2 format.
(#191) The license checker had a hard-coded limit of 32 licenses. Above 32 licenses, it failed ungracefully. Limit is now 100.
(#192) Changing the number of vertices in an SoVertexProperty node did not break the associated normal cache. Consider a QuadMesh with its vertexProperty field initialized with an SoVertexProperty node. Later, the number of points in the vertex array is changed. The normals should be but are not automatically regenerated. The result is a mismatch between the number of vertices and number of normals. In debug mode, lots of errors are generated. Ultimately, an incorrect picture was drawn.
(#195) Conflict between Po3DdataPrivate.h and SoG5GNurbs.h. They both defined Point3, resulting in a compile error. You could run into this problem if you tried to use TerrainViz and DataViz in the same app, or NURBS and DataViz together.
(#206) The SoBitmapFontCache destructor freed (by C++ delete function) a pointer allocated by C malloc (in libFL).
(#207) Large FaceSets crashed on NuTCRACKER.
(#208) There was a memory leak when large LineSets were removed from and then re-added to the scene.
(#209) Large TriangleStripSets crashed on NuTCRACKER.
(#210) Large IndexedTriangleStripSets crashed on NuTCRACKER.
(#211) System fonts weren't displayed on Linux (fixed by using a new libGLU).
(#212) Indexed shapes caused memory leaks when the coordIndex and vertex fields were modified.
(#214) A NURBS shape of degree 1 was unpickable with SoRayPickAction.
(#219) Memory leak on SoTexture2 node management. If you inserted, then deleted, then inserted, ... a SoTexture2 node to/from a scene, there were memory leaks.
(#221) (IVF, VisualStudio .NET) SceneViewer (and other IVF apps) built with VC 7 could not read .iv files that contained TRUE or FALSE values, e.g., solid TRUE.
(#226) Patterns and SCREEN_DOOR transparency broke the render cache, causing reduced performance.
(#227) OIV 3.1.1 textures used much more memory (x2-3) than OIV 2.6. There were performance and memory problems related to texture management.
(#229) IndexedLineSet crashed on NuTCRACKER 7.5 when too many indices were used.
(#230) (HP-UX) The license manager sometimes failed because it failed to get a hostid.
(#232) SoExtTexture2 export problems. If the loadStatus field was written to the iv file with value TRUE, when the file was loaded, the texture was considered as loaded and the delete of this texture crashed.
A similar problem occurred with the field loadingMode (when set to MANUAL). When the file was loaded, the texture wasn't displayed.
(#237) Mentor examples 17.2 and 17.3 missing missing from the OIV 3.1.1 for Windows installation. (Note: 17.1 is intentionally omitted because it has not been ported to Windows.)
(#246) The methods addChild and insertChild of the class SoGroup were not declared as virtual, preventing subclassing in some cases.
(#247) A manipulator above a VRMLBillboard node caused the geometry under the VRMLBillboard to be displayed incorrectly. The transform introduced by the manipulator caused the VRMLBillboard to not stay screen-aligned when the screen-aligned case was requested.
(#248) When a window was destroyed, its handle (stored internally in SoWin) was not set to NULL. This could cause a program crash when trying to open a second window.
(#249) The PNG import used too much memory.
(#252) Memory leak when SoDB::setNumRenderCaches was set to 0.
(#253) SoInput::addEnvDirectoriesFirst added directories to the search list twice.
(#255) The SoExtTexture2 node crashed (or went into an infinite loop) if the image file wasn't available.
(#257) Selection failed on geometry described with very small coordinates (around 10e-006). An environment variable, OIV_INTERSECT_EPSILON was added to allow specification of a smaller epsilon to allow these very small shapes to be picked.
(#259) WWWAnchor node with no children crashed SceneViewer when trying to view anchors (viewPoints menu).
(#268) Picking performance was slow in multi-thread environment.
(#269) SoXtFullViewer and SoXtMPFullViewer were missing the getStereoDialog and setStereoDialog methods.
(#270) IVF crashed in IvfImportDocument if IvfImportDocument was called when there was no scene graph in the doc class (i.e., m_pSceneRoot was NULL).
(#273) SoDecimationXXElements classStackIndex link error (prevented applications from using these elements).
(#275) The threadInit() method crashed in an ActiveX application. The SbPList registeredClassList was not protected by a mutex and caused a crash when the list was expanded while another thread was using the list.
(#279) In the Open Inventor VC7 installation, Open Inventor directory names were sometimes put into the VC7 directory list(s) incorrectly. Specifically, the Open Inventor directory name was sometimes concatenated with the last name in the list, rather than being given its own listing. This resulted in Open Inventor projects not building because the necessary Open Inventor files were not found.
(#280) The SoReorganizeAction::apply method failed when the reorganized scene root included only one child (non Separator).
(#281) The SoCollisionManager didn't work on SoTransformManip nodes if you modifed by hand the fields of this node.
(#288) SoFieldContainer::m_userData needed to be initialized to NULL. Also, the getUserData method of this class was made "const".
(#291) (Win32) Material Editor: If you attached a material and then showed the editor, the material editor did not display the attached material.
(#293) SoText2 strings were not correctly clipped at the left and bottom edges of the window. For a default left-justified SoText2 string, if the left edge of the string was moved outside the window, the entire string disappeared. This was very noticeable using the multi-pipe viewer because SoText2 strings that began on the left display should continue across the boundary onto the right display, but appeared to be "clipped" at the display boundary. Also seen in CAVELib apps.
For compatibility with current caching behavior, user must define environment variable OIV_CLIP_TEXT2 to get the new behavior.
(#299) If you used an SoImage node inside a PoView (or PoSceneView) the shape was not clipped against the specified view port.
(#305) Ref counts of the SoExtSelection node and the shapes increased each time SoExtSelection was called.
(#306) Most of the SoGroup methods weren't virtual. This meant that if one made a list of SoGroup pointers and put SoVRMLTransforms in it, the wrong addChild was called.
(#309) The SoOffscreenRenderer methods writeToJPEG and writeToTIFF did not delete the internal buffer correctly.
(#310) SceneViewer and TreeView crashed when an iv file that included an invalid SoTexture2::filename field was loaded.
(#313) The SoGLRenderAction::setUpdateArea didn't work. This method sets a GLUpdateAreaElement in the traversal state, which results in a call to glScissor to set the new area BUT the glEnable(GL_SCISSOR_TEST) was never called.
(#316) SoExtSelection selected objects that were behind the camera viewpoint.
(#321) SoCollisionManager failed when the path of the object was built by the SoPath::copy method.
(#322) There was bad precision on collision detection (even when SHAPE mode was used). The collision manager apparently stopped on "virtual" bounding boxes. It didn't stop on the shapes themselves.
(#325) The default OIV Suite download bundle nows include the material files for the Material palette.
(#326) Patterns were sometimes applied to the wrong shapes. Shapes that were defined in a graph before SoPattern or in another Separator were sometimes displayed with the pattern. This occurred when the scene moved (the initial display was correct).
(#328) (Enhancement) Material Palette Dialog: Colored spheres are now displayed with a higher quality transparency type (not screen door).
(#330) The VRMLTouchSensor did not activate the VRMLTimeSensor to drive the VRMLColorInterpolator when inside a PROTO.
(#331) (IVF) If a PoSceneView node included two SoTexture2 nodes loading the same file, the display wasn't textured.
(#335) The start/finishEditing methods didn't rescale textures. If the SoSFImage field of a texture node was updated between start/finishEditing calls, the texture was incorrectly displayed (this texture wasn't rescaled).
(#336) The error "SoPath::removeIndex(): Can't find parent node error" occurred erroneously. If you changed a node at the tail of a path that was created by searching for any node used a field used in an SoVRMLAppearance node, the program would generate the error, then crash.
(#338) Assertion problem in the demo SlotCar. The line:
assert(newTime > currentTime);
was replaced by:
assert(newTime > = currentTime);
(#339) The incorrect texture was displayed using JPEG export (SoOffscreenRenderer method writeToJPEG) when SoTexture2 and SoExtTexture2 nodes were mixed in the same scene.
(#359) (Linux) Open Inventor crashed when the stereo dialog box was closed with the X button.
(#364) The scale and shift operations of a SoTransformerManip class became incorrect if an SoUnits node was included in the manipulated scene.
(#369) The SoMPEGFrameRenderer::recordFrame method crashed when setFilePointer was called.
(#370) SoMPEGRenderer::getFilePointer returned an invalid file descriptor when openFile was called to open the MPEG file.
(#378) SoManipulator could initially fail to get the correct bounding box for geometry in SoWWWInline.
(#379) There was a memory leak when highlighted objects were animated (spun).
(#381) The VRMLTimeSensor did not send a final value of 1.0 when loop was FALSE at the end of the cycle.
(#388) Switching to DOLLY mode from PAN using the CRTL SHIFT caused the scene to jump.
(#389) Picking problem with SoMarkerSet, SoPointSet, and PoScatter within a PoSceneView. Using SoSelection node under two different PoSceneViews with pick filter callbacks attached, caused some pick filter calls however the point primitive (SoMarkerSet, SoPointSet, or PoScatter) was not selected.
(#392) SoIntersectingPrimitive detected a collision between a sphere and cone when there an intersectio of the bounding boxes, but not their geometry.
(#395) SoExtSelection crashed when the setTriangleFilterCallback set a user callback. This crash occurred in SbPlist even if the user callback did nothing.
(#396) TreeView program hung or immediately exited when loading a scene graph containing a node with a very long string in the string field.
(#405) SoMarkerSet::addMarker crashed when called on predefined indices without preliminary rendering.
(#416) SoMarkerSet didn't display markers in an MDI application when all documents were closed and then reopened.
(#420) (Enhancement) A new SoEXTENDER method clearOtherEventCallbacks() was added to SoDragPointDragger to allow suppression of the Ctrl-key behavior in SoJackDragger. Customer wanted to suppress the Ctrl-key behavior in SoJackDragger (switches to a different translation axis) because only one axis is valid and this behavior could confuse the user.
(#421) The stereo panel was unusable when the Motif context of the OIV toplevel differzs from the viewer's Motif context
(#425) Some geometry was not displayed because VRML inlines were not processed properly.
(#428) The Save button of the LargeModelViewer demo emptied the currently loaded file. The button was removed.
(#429) IVF programs could not set the default camera type. Normally an Inventor app can call SoWinViewer::setCameraType to specify whether an orthographic or perspective camera should be created if the scene graph does not contain any cameras. IVF overrides this feature and *always* creates a perspective camera. There is now a new method, CIvfDocument::setCameraType, equivalent to the SoWinViewer method.
(#430) There was a memory leak in SoIndexedShape.
(#433) There was a memory leak in the method SoReadImage::ReadJPEGImage.
(#440) In the IVF AppWizard, the SceneViewer option is now disabled if you are building a dialog-based app (because this combination of options is not meaningful).
(#444) If the from connection of a VRMLinterpolator wasn't an output of the Interpolator but from an exposedField that has an implied eventOut, the connection didn't work and a debug error was issued.
(#446) SoReorganizeAction (ivfix) had a problem when the material transparency field was NULL. In addition to the fix, various optimizations were added.
(#459) SoTransform::multLeft caused deadlock when SoDB::writeLock has been called.
(#462) During construction of an SoPickedPointList, the SoDetailList->copy was not copying NULL pointers that were in the SoDetailList, causing the SoPickedPointList constructor to be incomplete.
(#468) VRML files fitting the following profile could cause Open Inventor to crash:
- They contained multiple SoVRMLIndexedLineSets,
- AND the first line sets had fewer lines than subsequent ones,
- AND the colorIndex field was empty,
- AND the colorPerVertex field was FALSE.
The same problem could also occur with SoVRMLIndexedFaceSets.