Home Search

DriveWorks Solo 22
Bug Fixes

Send Feedback

We have fixed the following...

Thanks to your feedback, lots of new and updated code from our Dev department, and hours of testing by our Tech team, we've got some fixes for you too...

14100, 15127The addin in the SOLIDWORKS task pane is not maximised when first enabled.
16536Model Rules display the Tag property, reserved for DriveWorks Pro.
16564Using Find and Replace to replace a string, which is duplicated within the same rule, causes the application to crash.
16586Having whitespace within the rule for the SETTEXT function fails to drive Weld Symbols.
16632Driving a blank value into a captured drawing annotation leaves the original text in place.
16639Naming a control to be DriveWorks caused the application to crash.
16728The Show Only Missing checkbox in the capture assistant allows the same item to be captured more than once.
16764Driving an assembly saved in a SpeedPak configuration fails.
16795Switching between views causes minor memory leak.
16797List based controls do not retain their selection under certain circumstances.
16803Applying a Tab Index to a control allows it to be selected when the control is behind a control that has semi-transparency.

The fix implemented for DTI-16797 has resulted in a change in how list based controls (combo box, list box etc.) are evaluated during specification.

We recommend any controls that have dynamic list data (list data that changes on the result of other selections) is tested prior to going live.

DriveWorks Task Identification - A bug or accepted enhancement request is assigned a DriveWorks Task Identification to enable tracking of the item.