Here are a handful of interface bugs that appear very quickly when running through a 2D frame model. I have to ask is any testing done on Robot before it is released as these bugs are encountered almost immediately?
Members:
When adding members with the spreadsheet users must first select a material before you can select a section the column order does not reflect this as section appears before material this leads to users thinking the program is broken.
Sections&Materials:
If a user hits the "Esc" key inside the materials dialog the window deletes all contents and becomes unrecoverable.
(refer to attached GIF, come_on_robot.gif)
Supports:
Adding a support via the table results in a corrupt support definition where none of the degrees of freedom accept changes. In addition the list of nodes cannot be changed for the added support.
(refer to attached GIF, test_your_software.gif)
Robot seems like it could be a really nice piece of software but for every thing that makes me go oh cool it does that I hit 10 others things that make me question further use of the software. Almost everything feels half baked and it's such a shame because it seems at least the hard underlying algorithms and math behind the computations had same love put into it but the user interface which comparatively feels as though it should have been the easy part to code feels clumsy and half hearted and constantly makes us question if the hard stuff was actually done right or not.
