INDRA ESPACIO Juan Carlos Martin SW Tool: HP-VEE V3.2 We have been using new version V3.2 of VEE tool and we have discovered some problems which should be fixed in later versions. These are new problems because they did not appear in old version V3.12. The procedure to get a SYSTEM ERROR is the following: 1. Create a UserObject1. 2. Create any object, for example an AlphaNumeric Display. Insert this object into UserObject1 and add it to their panel. 3. Create other UserObject2. 4. In detail view, include UserObject1 into UserObject2. 5. Add UserObject1 panel to UserObject2 panel. Then at panel view, we have a panel which have other panel including a Display. 6. Go to detail view of UserObject2 and maximize it. 7. Go to detail view of UserObject1 and maximize it. 8. Cut AlphaNumeric Display object from detail view of UserObject1. 9. Go to panel view of UserObject1. Logically, here also the Display has been cut. 10. Go to panel view of UserObject2. Here the Display has not been cutted. If you try to put the mouse pointer over the object you will get a 999 error. We have made some tests and we have discover the following: - A system error appears always in the highest level panel object when the design have more than 2 levels in the panel view. - The error is related to "maximize" action. That means that when this procedure is followed without passing through points 6 and 7, the error never appears. - If after removing the Display object and before passing to point 10, a new object Display2 is generated and added to panel of UserObject1, when UserObject2 panel is shown VEE do not crash. Moreover, UserObject2 panel 'adopt' the new object, Display2, as it were the old Display. - If the before procedure is followed but deleting two objects from detail of UserObject1 and adding a new object into their detail and panel views, VEE do not crash. Instead of that it provide a message similar than this: Value 3 out of bounds (valid range=[0..2]) Error number: 401 And all objects included in UserObject2 disappear but VEE apparently can continue working without problems. >From our point of view, the problem is very important. It is because if you are working in a low level detail view with a UserObject maximized, you cut some object included in a other higher panel view and try to save (before pass to this higher UserObject panel view) VEE saves the program only until it find this problem. The new saved version file is cut until this point and it cannot be used again. The file with changes also cannot be saved with any other name: Changes are missed. And if you make the mistake doing the same with .bak file and try to save it, you will miss all design information. SUGGESTION On the other hand, we think that some objects (display objects, for example) should have a 'fixed properties' switch. In this way if the switch is put ON (at detail view), all the properties changed in a view (in some panel or in the detail view) are changed in all views. This could avoid time, because many times an object is added to a chain of panel into other panel, one or several times but with the same properties (for example, Number or Fonts). Currently, if you want to change the object properties, you must to change their properties in the same way in all panels. If you have an object in a panel into other panel and after being included in both panels you change their properties only in the higher level, when for other things you change the lower level panel view and you try to add it to the higher level panel you miss the modified properties of the original object, because they did not were changed in the lower level panel. To avoid that it is necessary to change the properties in all panels one after other at the same time. If you put the switch OFF, VEE could works as currently and you could have the same object twice into the same panel but with different properties (different Colours, for example). You want to display the same information with the same object but in different places and in different way.