\\\"A) The dialog control elements are not consistent in respect to the used form buttons, popups and menus. A1) An unexperienced user have troubles to manage large archives. Demonstration by the following example: 1) Open a large archive which was generated by adding a lot of components. 2) Push button ADD to add another object. User selects and accepts it. (The user is now waiting a very long time until he can continue the dialgue) 3) User saves the archive. The reason for that behaviour is the implicit complete data retrieval from the archive database table before adding an object. The user is wasting time on trials before detecting that it is better to clear (only in the popup panel) the form before adding new objects. Thus if there is an ADD button there must be also a CLEAR button. Missing is also a warning if there are a lot of unretrieved occurences. A2) The field \\\"\\\"object type\\\"\\\" have to offer in the clear state a drop down like it is available in field selection scope. The user have to learn e.g. typing in EDC as profile string yields to \\\"\\\"Entity Descriptor\\\"\\\". B) Saving selections in the archive itself The quick selection form and other selections are helping the user to add objects to the archive in a quick way. But the development goes on and there will be created new objects falling into the scope of the selections. Now the user have to perform all quick selections again to achieve an archive up to date. If some designated selected selections would be stored in the archive itself, the user would only push a button \\\"\\\"Up to date by stored selections\\\"\\\" leading to the necesarry actions for adding and compiling the concerned objects. The result is an archive up to date.\\\"
\\\"1) Adjusting the buttons to panel items 2) New button \\\"\\\"store selection in archive\\\"\\\" in quick selection form and add object form.\\\"
Facilitate managing archives.
Uniface Development Environment