Improvements
Versa now maintains the focus on the selected item on the Interface and Inspected Units screen when you use "Copy Item".
- Other screens that have copy item will get this improvement as well soon.
Copy Item on the Interface now lets you create the copy by hitting the ENTER key on your keyboard.
Added a note to the Copy Item window on the Interface suggesting you to use Add Multiple Items (the button for it is on the Ribbon) if you are trying to craete multiple line items quickly.
We improved the performance of the Interface when clicking on line items and using Components or Component Types by reducing the number of database calls.
- Initially Versa was using "lazy loading" for a lot of the data on the Interface. This meant it would load things only when it needed it. Unfortunatley this caused the Interface to be more talkative with the database server.
- In order to reduce the chattiness of the Interface and the database, Versa now requests all Interface Items with their alternatives and all Components with their other details when the screen loads.
- Note that certain operations still require database communication (copying items, saving, etc.)
Versa has been updated to use version 5.0.3 of .Dot Net to ensure it has the latest security and other bug fixes from Microsoft.
- This does not require a Windows Update or system update of any kind. Versa will automatically update the framework version it uses on your computer when you run it for the first time.
Bug Fixes
- While we are not 100% certian this bug is fixed, I spent some time investigating a possible problem where the Interface screen's selected item could become out of sync with what Windows thinks is the selected item on the Grid.
- The following changes were made to POTENTIALLY address the above:
- Copy Item on the Interface has been re-written and adjusted so that it doesn't run into a possible bug where it can create invisible bogus items.
- Copy item now uses a dialog window instead of a regular window so you can't click and hide it by accident to create possible weird bugs.
- We removed a werid piece of code that was in the method for setting the selected item on the Interface. This weird piece of code could possibly cause the bug. The reason it was was there was for dealing with an older problem that is no longer an issue.