DialogViz - Fixed bugs

DialogViz Fixed Bugs

7.2 Final Release

7.1.1 Patch : Bugs fixed as of June 28, 2008

7.1 Final release

Patch 7.0.1: Bugs fixed as of February 20, 2008

(#2149) Viewer is not correctly attached to the parent frame, on first rendered frame.

7.0 Final release

(#2061) DialogViz didn't properly update the bottom of dialogs that didn't fit on the screen.

Patch 6.1.2: Bugs fixed as of July 19, 2007

Patch 6.1.1: Bugs fixed as of May 29, 2007

6.1 Final release

Patch 6.0.3: Bugs fixed as of December 4, 2006

Patch 6.0.1: Bugs fixed as of July 12, 2006

(#1091) A call to QMessageBox::information crashed or terminated the application. [P1]
(#1092) SoMessageDialog didn't display any message in the Qt environment (because it wasn't implemented). [P1]
(#1505) SoDialogViz::setSkinsDirectory didn't support absolute paths. The skins directory could only be specified relative to the current directory or to $OIVHOME/data/DialogViz/skins. [P1]
(#1506) DIALOGVIZ_SKINS_DIR didn't support a partition other than C:. [P1]

6.0 Final release

Patch 1.1.5: Bugs fixed as of October 2, 2005

Patch 1.1.4: Bugs fixed as of June 6, 2005

Patch 1.1.3: Bugs fixed as of March 11, 2005

(#1081) The 3D SoDialogRealSlider did not display the cursor at the position selected with the mouse. [P3]
(#1082) On the 3D SoDialogRealSlider, the slider callback wasn't called when the button press and release defined the same slider position. [P3]

Patch 1.1.2: Bugs fixed as of December 10, 2004

(#881) Delayed and sorted transparency types failed when used with transparent DialogViz 3D menus. When SORTED_TRIANGLES_BLEND was selected, DialogViz crashed as soon as you tried to use a DialogViz component. With the other transparency types, the image flipped when the mouse cursor moved on the DialogViz sliders. [P2]

Patch 1.1.1: Bugs fixed as of October 8, 2004

(#883) Object selection output error messages when a DialogViz 3D menu was displayed. The ray pick action was traversing DialogViz nodes, but since no path was found, Open Inventor was generating a warning message. [P1]

1.1 Final release

Patch 1.0.6: Bugs fixed as of January 20, 2003

Patch 1.0.5: Bugs fixed as of November 10, 2003

(#610) At runtime, adding, inserting, replacing, or deleting children in SoColumnDialog, SoDialogCheckBoxLauncher, SoDialogPushButtonLauncher, SoMenuBar, SoMenuCheckBoxLauncher, SoMenuPopup, SoMenuPushButtonLauncher, SoRowDialog, SoTabDialog, and SoTopLevelDialog could cause segmentation fault or dialog windows update problems. [P5]
(#611) Changing the selected page made the SoTabDialog component shrink and then recover its correct size. [P5]
(#612) If you modified the enable field value of a SoTabDialog component, the change was not applied to the visual component. [P5]
(#613) [UNIX] There was a DialogViz memory leak on UNIX that occurred with all components. [P5]
(#614) Dialog window size problem when using a MenuBar. When using a SoMenuBar node as a child of a SoTopLevelDialog, the lowest component of the window was truncated. [P5]
(#615) If a child of the SoTabDialog component had its labelVisibility field value set to FALSE, the generated window had an infinite size. This happened only when the field was set to FALSE before the dialog window was built. [P5]
(#616) SoMenuFileSelection filter problem. When defining several filters to the SoMenuFileSelection node, only the first one was considered. [P5]