Inline math operations on the current value

Serengeti (Rhino WIP)
1

So I had this shortcut idea randomly when I was modelling…
There should be an enhancement made to the inline math operations so that if you are doing some offsets and the current offset is set to 45, you could simply type something like *2 and it would use the current value multiply it by 2, and return 90.
It would be really handy for when you are doing a lot of the same operation but changing the values incrementally or for when you type in a number and forget to type the operation before pressing enter.

2

Hi Jesse, That’s a feature already.

https://docs.mcneel.com/rhino/7/help/en-us/index.htm#user_interface/command-line_calculator.htm?Highlight=formulas

3

Correct, typing in the entire math expression, and I was thrilled when that feature was added!
I’m talking about after the value is set, starting with an operator would automatically use the set value for the first operand.
So if Offset is set to use 20 as its value then typing /2 would set the value to 10. You wouldn’t have to type 20/2.

4

Gotcha, i can see that being useful, kind of like you can do in the gumball Move for instance.

5

Yes, exactly!

6

In the offset example it would need to be after entering into the Distance variable. Currently the command is Offset ,SideToOffset (or enter variable). Is that how you see it?

7

I believe that is so if I’m understanding you correctly. In the offset example, the last value entered is the one that is defaulted when the command is rerun. At least that is how my system runs. I’ve never really paid a lot of attention to the default values that commands hold, but I feel like most of the ones that I have run always have a default value.

However, thinking a little more about it, there would probably be edge cases where entering a shorthand like +3 wouldn’t have a valid value to glum onto. In which case, it would have to just “unknown command” out like what happens when you enter the wrong type of value into a command

8

To clarify what I’m thinking a little more, whatever parameter gets filled when you fire a command and enter a number or expression, would be the same parameter that would get modified if you entered “operator operand” instead of a regular number.