I recently experienced a file corruption that caused me a great deal of time and trouble. A class I created somehow became the default class, and many of my PIO objects and all new groups (v10.5.1) were automatically assigned to this "renegade" class. Among the many other little difficulties this creates: the Wall Type dialog box no longer listed "None" as a class assignment option, but instead listed my renegade class.
Technical support says they can't track this bug down, and I don't fault them. But, to prevent this happening, VW should be modified so that it is impossible for the default class to be renamed or otherwise substituted, either deliberately or through internal error.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
P Retondo
I recently experienced a file corruption that caused me a great deal of time and trouble. A class I created somehow became the default class, and many of my PIO objects and all new groups (v10.5.1) were automatically assigned to this "renegade" class. Among the many other little difficulties this creates: the Wall Type dialog box no longer listed "None" as a class assignment option, but instead listed my renegade class.
Technical support says they can't track this bug down, and I don't fault them. But, to prevent this happening, VW should be modified so that it is impossible for the default class to be renamed or otherwise substituted, either deliberately or through internal error.
Link to comment
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.