![]() ![]() (Again, McNeel has a good record here, too). And a valuable way to identify areas for improvement is if frustrations are sought, expressed, and given a degree of consideration without too much defending of the existing solutions. As such, there is value in always considering if better ways can be realized. I’m as guilty as the rest in this! However, in the quest for new users, constant improvement (and McNeel has a very good track record here!) is rewarded in the marketplace. Often it is what we have become (ab)used to that makes existing methods seem immutable. I realize the inherent difficulty of questioning existing methods to those intimately acquainted with existing software. Seasoned Rhino users will possibly have deciphered the nuances required as things are (and I’m not convinced of this based on many conversations I’ve had with others about rhino snaps) however, the reality is that new users are often baffled by snaps/ortho/planar in their totality. I’m merely suggesting that they could work a whole lot more easily and intuitively-especially, it seems to me, if hotkeys could be dynamically used (as is the case in PowerCADD, who handle snaps better than any other program I’ve encountered). ![]() To be clear, I’m not suggesting that the snaps “don’t” work or “can’t” work as they are. Add to the mix the Planar and Ortho toggles (in various combinations of being on/off) and snapping becomes more complex than is needed, in my opinion, with lots of mousing involved for changes when things don’t work out as desired. I hear you, Mitch, and I’m glad the snaps work for you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |