Hello everyone, I would like to suggest that the number that appear in gumball functionalities whenever it is clicked, could have a brief history for such like 3 numbers or be able to control the history number in options
I proposed this particular feature numerous times over the years, but the developers were not interested in improving the Gumball in this regard.
If you check my last link below, you will find a way to set two numerical values per custom icon. If you regularly use specific values, you can create several custom icons and set those numbers inside.
Maybe they lost this part on your posts since they seem super dense in all it is requested there. At least I hope so, since what I am suggesting seems to be way simpler than what I briefly saw in your posts.
This is just a small portion of my proposals regarding the remembered values. The Rhino developers haven’t “lost” anything. They read my posts perfectly fine and are aware of my feature request. I got replies by them and the answer was that this is not going to happen in Rhino 7 and Rhino 8. Perhaps not even Rhino 9, though I still have some hope that they will add this feature in a future Service release, such like Rhino 9 SR3.
Man, from what I read in your posts you made a ton of requests and they are way more complex, even the history method for gumball you shared. Mine is already there, they could just provide an option so you could have X instead of only one history option in gumball
Thanks for the suggestion. We do have a number of feature requests in this regard. I’m going to have the gumball dev review this thread to make sure we are all on the same page.
Why are you deeply sour about my proposals? For the second time. 
There is nothing “way more complex” in my proposal regarding the remembered numerical values. My proposal is detailed, perfectly easy to understand, and the sample image shows a very easy implementation using the existing dot objects in Rhino.
hahahahahaha not even a bit sour bro, stop playing victim. I just said that is more complex what you requested than what I did. Did not said anything with a bad vibe on it.
My proposal covers the remembered numerical values for both, the Gumball and other tools such like “Fillet”, “Move”, “Rotate” etc. It’s about offering an automatic pop-up list with the last used values next to the mouse pointer using dot objects. Super useful when you have to create fillets, too.
A vertical list with the numerical values is way more usable than any other type of listing these, because some values may include longer numbers. Also, a vertical list is easier to click and recognize at first glance.
Here is how “way more complex” is my proposal:
- Activate a command that’s compatible with the “remembered numerical values” feature, such like “Fillet”;
- Rhino brings a pop-up list with the last used values;
- You have the ability to directly pick one of the values, then pick the surface edges or curves;
- Rhino create a fillet with the chosen value.
So basically you would have to have history in hold for all commands instead of only gumball.
My proposal is universal, so it’s up to the developers whether they will implement it only for the Gumball, or will also include certain tools that will heavily benefit from remembered numerical values. Once it’s implemented, it would be easy to expand it to more user cases.
The core approach is the same: a vertical list of last used numerical values rendered inside regular dot objects. The dot objects are already used by many scripts and plug-ins.
Ok, nice, but is way more complex and memory consumming
Storing a few numbers in the memory is nothing in comparison with storing 1000 undos with ton of geometry in Rhino. 
Not to mention that if you only use Gumball and/or the “Move” command in your modeling session to move objects (and don’t use “Fillet” or other tools that could benefit from the remembered numerical values), Rhino will consume exactly the same amount of numbers like what you have proposed.
However, your proposal does not include the “Move”, “Scale” and “Rotate” tools, which is a huge limitation, because in many cases it’s necessary (or way more convenient and precise) to use these instead of Gumball. If you move something by 15,7 mm with Gumball, you will not be able to use the same remembered value with the “Move” command, because your proposal is lacking it.
My proposal may sound “way more complex” to you, because it includes these tools, along with “Fillet” and others, but it’s way more usable. No idea why you act this way since the beginning og the topic and can’t see the benefits.
you never crashed rhino while doing an undo?
Even the 30-years old “Casio” calculator of my father can’t crash from storing a few numbers…
My PC is quite old (2014), yet it handles 3dm files up to 2GB and hundreds of undos with complex NURBS geometry. A few numbers in the memory are like a drop in the ocean.
without crash? 128gb memory?
4x 4 GB DDR3 (16 GB total).
Do you have a proof that a few stored numbers can crash Rhino? I’m asking you, because your proposal is a limited version of my proposal, and in an earlier post you were worried that a few numbers can crash Rhino. You expect that numerical values stored and used only by Gumball will not crash Rhino, but if stored numbers are used by any other tool, they will crash Rhino? How is that possible?
Yesterday, I stored several complex 3d NURBS models with dense render mesh while working with Rhino 7, and I used hundreds of undos while the geometry was still stored in the memory for hours. Despite that, my Rhino didn’t crash. I doubt that storing a few extra numbers will crash it.
On top of that, many tools in Rhino already store the last used numerical values, so whether Rhino stores 100 numbers or 105 numbers, it does not matter with the modern PC machines. Rhino even stores much more complex data, such like full parameters of individual objects that are History-enabled. Also, it stores the complete settings for tools like the new “Patch” in Rhino 9 WIP.
Not to mention that nearly all CAD programs store the used numerical values for every object. Solidworks and Fusion 360, for example, both remember every single fillet, movement, rotation, scale etc, in order to provide a full history tree and ability to change the parameters later.
If that’s not enough for you to believe that a few numbers can’t crash Rhino, I will remind you that Rhino also has the ability to store numbers, text and other characters into its Notes (an integrated Notepad). Imagine if the last few used numerical values are stored into a similar alternative version of Notes, used for this particular purpose. This will release a few dozens of bytes from the RAM.