Home Search

DriveWorks Solo 22
Bug Fixes

Send Feedback

Introduction

This section details all fixes to existing functionality and minor improvements to usability.

DriveWorks Solo Project Designer

DTIDescription
5176In many of the document editors, #VALUE! is displayed as a long negative number instead of as #VALUE!
5482The descriptions for the functions TableGetColumnCount and TableGetRowCount are the same.
5504Spin Buttons do not correctly work with decimal values in non-English cultures which do not use a decimal point as the decimal separator.
5547Long text lines overflow underneath the vertical scroll bar in the DriveWorks Rules Builder
5606Copy and paste commands sometimes crash when using the Simple Data Table Editor
5671It is possible to completely hide the forms list in the Form Designer, by dragging it to the smallest size possible and letting go. After this the Forms List can never be resized as it has no size
5681Picture based controls on DriveWorks Forms can take a long time to load
5685Picture controls that use a web browser to display their files can appear outside of the form and scroll area
5688Dragging and dropping variables into categories, if you drag a variable to the bottom of the list it will auto scroll to allow you to drop it into its category, it doesnt autoscroll if you drag upwards.
5879Tabbing into a DriveWorks Form Control that has a text box does not select all the text in the box
5916Deleting a form shows the prompt "Are you should ..." instead of "Are you sure ..."
5978Hitting finish in the ListAllConditionalDistinct function in the Rules Builder when there are no DriveWorks Tables in the Project, causes DriveWorks to crash
6177DriveWorks Application crashes when deleting a form step. If the form designer section had been viewed beforehand.
5471During the Solo Generation or Preview Process, DriveWorks crashes when models have been created in a later version of SOLIDWORKS
5512When a Project is renamed in DriveWorks Solo, the DWSpecification Special Variable used for naming models and folders still uses the old Project name
5610In DriveWorks Solo, changing a feature's capture information, then running a project, and returning to finish editing the feature information causes a crash.

Licensing

DTIDescription
5970DriveWorks License Management Tool is not uninstalled/removed from start menu when you uninstall 8 SP2.
6193The licensing wizard should indicate when a code is for a different product
6194The licensing wizard should indicate if someone has entered an example code
6195The licensing wizard should indicate if a code has been entered for the wrong version of DriveWorks
6196The licensing wizard should indicate if the product count section of the code is non-numeric

SOLIDWORKS and Model Generation

DTIDescription
5514After capturing a view, if the view's scale is changed from custom to inherit, or vice versa, DriveWorks still uses the old value until the view is uncaptured and recaptured
5583Advanced Feature Parameters are missing for Circular Patterns in an Assembly
5743Driving the color of a model also removes its texture
5757During generation, the generation dialog sometimes appears showing the text "Lorem ipsum..." before changing to a meaningful description
5769Layout mode crashes in SOLIDWORKS 2011 SP4
5930In certain advanced cases where features are interdependent, SOLIDWORKS cannot delete the features in a single operation. DriveWorks now detects the situation and deletes in several operations.
6169Uncapturing a view which has been deleted in SOLIDWORKS, and whose parent sheet isn't captured, causes a crash
6214Layout mode in DriveWorks Solo causes SOLIDWORKS to crash if you cancel a previewed specification, and then preview another specification of the same master model.
DriveWorks Task Identification - A bug or accepted enhancement request is assigned a DriveWorks Task Identification to enable tracking of the item.
DriveWorks Task Identification - A bug or accepted enhancement request is assigned a DriveWorks Task Identification to enable tracking of the item.
DriveWorks Task Identification - A bug or accepted enhancement request is assigned a DriveWorks Task Identification to enable tracking of the item.