Steven,
1) Front, Back, Left, Right, Top and Bottom views all reset when I select them after I do an Arc Rotate to adjust the view temporarily. Ortho and Perspective do not. At the risk of being impertinent, may I ask why? It's not a huge problem. I know how to use the view menu to reset them. I'm just curious why that behavior exhibits? Remember, I used to break code for a living (and a fair living it was, too) so I have a knack for finding chinks in software's manners.
2) Suppose I have a shed load of edges or faces selected and am having to individually select the faces I want using right-click. I am old and my hand-eye coordination is not the best any more. So I have a whole bunch of edges/faces selected and my hand shifts the tiniest bit and I accidentally select an edge/face I did NOT intend to select. BUMMER! So far as I know the only way to UNselect said edge/face is to click on empty space and start all over. IS there an easy way to UNselect a single edge/face while keeping all the others I have so painstakingly individually selected?
Maybe something to put on the to-do list for V1.01?
Oh and while I have your undivided attention: I was building a long spline the other day and managed to put an end somewhere I did not want to. I did a Ctrl+z to undo the last spline segment (probably the 10th or 12th). Anim8or gave me a super quick error message (didn't have time to really read it much less jot it down) and promptly crashed. If you like I can try to reproduce the error. As a software test tech I would categorize any error which induces software to take its tinkertoys and go home as Category 1- Major. Software is not allowed to leave until the user dismisses it. Nothing made by human beings is perfect and software is no exception. But no software can truly be exhaustively tested. I once read a paper where the PhD author calculated that to exhaustively test a program to implement a 4-banger (add, subtract, multiply, divide) calculator would require a significant percentage of the lifetime of planet earth. That's why a (good) tester first confirms that the software first does everything it's supposed to do then starts poking around at the edges to see if it has any bad habits waiting to be exposed by user input. A wise man once said that "The devil is in the details."
