A General Comment


#1

I’m now aware that History is on by default along with annotation scaling in V6. And annotation scaling, as of this moment, can’t be turned off. Unchecking this function doesn’t have the same result as it does in V5. I don’t use scaling in V5 and I rarely, if ever, use history.

So, I want to register my request that the simple, basic, flexible nature of Rhino not be lost in the shuffle on the way to V6.

I think sometimes developers aren’t as aware of the actual usage of their software as they should be. For instance, I’ve probably worked with 20 people over the years who use AutoCAD and I’d say 15 of those twenty don’t use annotative scaling. But if you listen to the developers on their forum you get the impression that anyone who isn’t using annotative scaling is ‘doing it wrong’. But how the software is used should be left up to the user and there shouldn’t be obstacles put in their path to force them to conform to some pre-determined concept of correct usage.

Currently I only play around with V6 when I have a moment because my workflow cannot be replicated in the WIP. Let me repeat that - the fundamental workflow that I’ve developed over the last few years while transitioning from AutoCAD to Rhino, that works for me, that is profitable for me, cannot be replicated in V6. I think that’s a bad sign going forward. Respectfully, I hope the developers can take a moment to ask themselves to be more familiar with how users actually use V5 and not create impediments to doing the same in V6.


(Wim Dekeyser) #2

Note that the annotation scaling will be different in the next WIP. Rhino 5 behaviour should then be possible again. So, please make sure to test that one.

Is the history for annotations causing you problems?


#3

I’m aware that some of the things I complained about are being addressed in upcoming releases. My intention was to comment on the general direction of development using a couple of obvious examples with the hope that those of us who don’t use all the bells and whistles are not forgotten going forward. To put it as simply as possible - the simplicity of Rhino should not be shouldered aside in favor of new, more complex features.

As far as history and dimensions - yes, it’s not working for me - currently dimensions do not move with geometry.


#4

Totally agree with Alex. Keeping the good, but more rarely used, features “under the hood” (but not so far under that no one can find them) is good.

And… as far as annotative scaling is concerned, I work in Layout all day, five days a week (sometimes six) and I never use it. It obviously has its place and it’s great that it’s there but it seems to have created a lot of confusion around it.