TABLE OF CONTENTS
This Release
This release of V6 introduces few enhancements and fixes a few issues.
Enhancement
| Details | Reference | |
|---|---|---|
| 1. |
Add macro exposure for 'DetectReferencePointCollision' Requirement: As a V6 Macro writer I want to drive the state of the 'DetectReferencePointCollision' property in Frame from a macro so that I can control the usage of the feature. Implementation: Added macro support for the DetectReferencePointCollision frame property. Macro writers can now enable or disable this feature programmatically, allowing greater control over reference point collision detection directly through V6 macros - consistent with other already exposed frame properties. Test Macro: '#Language "WWB.NET" Sub Main FrameDesigner.Frame.DetectReferencePointCollision = True. End Sub |
228095 |
| 2. |
New COM exposure for engineering validation results Requirement: As a Catalogue Developer for Dealer, I need an improved method for retrieving and organizing engineering validation results so that these results can be accurately presented back within a Dealer Quote. Implementation: A new COM interface has been added to V6.FrameObject to provide full engineering validation details for Dealer. Unlike the previous COM method - which always returned a generic static message - the new implementation exposes complete validation results, including pass/fail status, messages, and all UI-visible strings, using a structured JSON output format. |
226954/227366 |
| 3. |
Extend Lookup Matrix return field to accept strings up to 1000 characters Requirement: As a database developer, I need the ability to store larger text values in a lookup matrix field that is used to capture quote‑specific information. When a lookup matrix is configured with a return type of Text, V6 saves the entered cell content into the gen_value column of the matrix_cell_gen table. However, this column is currently limited to varchar(120), which restricts the amount of information that can be stored. Implementation: The GEN_VALUE field in the MATRIX_CELL_GEN table was successfully extended from varchar(120) to varchar(1000) to support larger data values. Test Case: Access V6 → Resources → Lookup Matrix, then create a new Lookup Matrix or edit an existing one, set the Cell Data Type to 'Text'. Navigate to the Matrix tab and enter a paragraph of up to 1000 characters in the Option or Description cell to verify that the field now supports the expanded character limit. |
227503 |
| 4. |
DEALER VRML Enhancement Requirement: As a designer or engineer using V6, I want the 3D export system to support both VRML and X3D formats with improved geometric accuracy and material representation, so that I can generate high-quality, realistic 3D models suitable for modern visualization platforms. Implementation: This release delivers a major improvement to the 3D model export system within V6, focusing on the long-standing VRML export functionality and introducing support for the new X3D format. These changes modernize the output, dramatically improving geometric accuracy, material representation, and visual quality. |
227577 |
Database Updates
| Details | Reference | |
|---|---|---|
| 1. |
The database has been updated to 21583. ALTER TABLE MATRIX_CELL_GEN MODIFY GEN_VALUE VARCHAR2(1000); This changes the column definition from VARCHAR2(120) to VARCHAR2(1000) to support larger data content. |
228111 |
| 2. |
The database has been updated to 21584. SQL Server: ALTER TABLE ASSY_HOOK_GASKET ADD FINCOL_ID INT NULL; ALTER TABLE ASSY_HOOK_GASKET ADD CONSTRAINT FK3_ASSY_HOOK_GASKET FOREIGN KEY (FINCOL_LIB_ID, FINCOL_ID) REFERENCES FINCOL (FINCOL_LIB_ID, FINCOL_ID); |
228139 |
| 3. |
The database has been updated to 21585: Created additional RES_TAG_LINK indexing structures.
|
228174 |
Fixes to Known Issues
| Details | Issue Reported/Introduced in Version | Reference | |
|---|---|---|---|
| 1. |
Lockbox snapping to the SDL Grid is causing a V6 Assert and Access Violation error in one of the customers’ databases Symptom: As a user, I want the lockbox to snap to the SDL Grid without triggering errors, so that I can align Lockbox elements reliably in the design interface without the application crashing. Currently, attempting to snap or align a lockbox to the SDL Grid in one of the customers’ databases causes V6 Assert and Access Violation errors, leading to an unexpected crash. Resolution: The issue causing a V6 Assert and Access Violation when snapping the lockbox to the SDL Grid in one of the customers’ databases has been resolved. |
3.80.56.1010 |
227436 |
| 2. |
Extra assemblies After Split light on lockbox frame Symptom: A customer lockbox frame becomes corrupted after running a split light wizard. Two incorrect extra assemblies appear in the red‑highlighted area after the split light operation. Resolution: The issue where a lockbox frame generated incorrect geometry after running the Split Light Wizard has been resolved. The fix ensures the lockbox no longer overruns into the wireframe and no extra assemblies are created. Geometry now generates correctly without requiring manual adjustments. |
3.80.76 |
227441 |
| 3. |
Cannot remove Printer Driver once entered Symptom: In Settings → Options → Printer, when a user enters a value for Letter Head or Label driver, there is no 'X' or clear button to remove or reset it. Resolution: A clear (“X”) option has now been added for Letter Head and Label printer driver fields. |
3.7, 3.8 |
183948 |