PR257461 - The dimension dialog does not keep the user axis selection

huangyhg

257461 - The dimension dialog does not keep the user axis selection
<< Werner Habermann  --  10/04/08  17:55:07>>
That's not acceptable from a user point of view. I see three mayor problems here where the dimension dialog does not keep the user axis selection:
1. After the serialization/deserialisation all dimensions have the AUTO axis checker enabled even if the user has made a different axis selection.
2. When the user adds a new dimension command with his own axis selection and opens the dialog of a dimension command with AUTO axis selection then the F9 on the new added dimension command also shows     AUTO axis selection.
3. When I uncheck the AUTO axis selection the axes that are checked in the disabled state turns off.
If I would have to work with this daily it would drive me mad. Please fix this before we release.
1. Steps to duplicate:
Create a new dimension command and select user defined axis
Close and open the pp
Result:
AUTO axis is checked (1:52)
Expected result:
The user has defined own axis selection. The dialog and his selected axis should be in sync.
2. Steps to duplicate:
Add a new dimension command
F9 on a dimension command where AUTO axis is checked
F9 on the new added dimension command
Result:
AUTO axis is checked (2:28)
Expected result:
The user has defined own axis selection. The dialog and his selected axis should be in sync.
3. Steps to duplicate:
(1:56)
Result:
AXES that were checked on the disabled controls gets unchecked.
Expected result:
Keep the users selection. This unproductive clicking to the wanted axes selection again and again must be stopped.

Steps to reproduce:

<<END>>


<< Don Turcotte  --  10/15/08  11:22:56>>
From Dave:
"Back saving into V43B from V44B looks like the setting is lost when it should still be supported.
"
When you File/SaveAs from V44B, the schema is a V43R schema since this is the last released version of V43.  Since the serialization code that I added is not in the V43R nor in the V431 versions this will be an issue.  If my changes are merged into V431, then when V43 MR1 is released and File/SaveAs from V44B saves using a V43 MR1 schema this would no longer be a problem.
I believe my changes are correct given that these changes are not in V431.
<<END>>
<< Changes made by Don Turcotte -- 10/15/08  11:23:08>>
Action:  Don Turcotte to David Petrizze, Status:  OPEN to REVIEW
<<END>>
<< Don Turcotte  --  10/14/08  11:49:11>>
Sent e-mail to Dave:
Dave,
Your comments here "Don, are there going to be issues with serialization ranges between V43B and V44B?  Based on the code changes, I don't think we've covered all the cases."
I don't understand what you think is missing here.  What cases are not covered between V43B and V44B?
<<END>>
<< David Petrizze  --  10/13/08  09:10:47>>
Don, are there going to be issues with serialization ranges between V43B and V44B?  Based on the code changes, I don't think we've covered all the cases.
<<END>>
<< Changes made by David Petrizze -- 10/13/08  09:10:56>>
Action:  CMM Group to Don Turcotte, Status:  REVIEW to OPEN
<<END>>
<< Don Turcotte  --  10/07/08  08:49:25>>
Fixed in V43B, V44B by serializing the m_auto flag.
Files inserted to server
------------------------
V43B\DIMENS\START_LO.CPP
V43B\INCLUDE\GLOBALS.H
V44B\DIMENS\START_LO.CPP
V44B\INCLUDE\PCDSCHEMA.H

<<END>>
<< Changes made by Don Turcotte -- 10/07/08  08:50:08>>
Action:  Don Turcotte to CMM Group, Status:  OPEN to REVIEW
<<END>>
<< Don Turcotte  --  10/06/08  17:10:23>>
I have been able to duplicate this problem.  The basic issue here seems to be that the m_auto flag is not serialized.
<<END>>
<< Changes made by Neil Kay -- 10/06/08  17:31:05>>
Category:  UI-Dialogs to dimensions, Action:  Systems Group to Don Turcotte, Assigned:  Systems Group to Don Turcotte
<<END>>
<< Changes made by Tim Wernicke -- 10/06/08  07:58:50>>
Priority:  to Critical
<<END>>