@innovatenate,
It makes me feel better knowing I'm not the only one that can't make parameter values work. It can be frustrating spending hours on something like this, just to find out it is not fully implemented yet.
I'm not going to bother with the idea station, because it's just a black hole. If the tool tables were finished with materials, I probably wouldn't need to alter the expressions to get proper paths.
Plus this isn't an idea, it's a bug or broken feature. It should just be fixed.
I can't imagine any possible scenario where a person needs to see a feed per tooth down to the 0.000000000 th digit. All those extra numbers just make it confusing and WAY to easy to make a mistake. It also looks very amateur to see the fields laid out this fashion. At a quick glance, 0.0002568988995 could very easily be mistaken for 0.0025689889953. In comparison, 0.0002 vs 0.0026 makes it a lot easier to see what's happening. also remember, there are about 10 of these unruly fields in each form!
You don't see these 12 digit long numbers in the model environment, why is it acceptable in cam?
Fields that are directly tied to another field should be grouped together to further reduce any confusion. For example, spindle speed and surface speed should be grouped, because they are directly linked. You could use either of these fields to get proper results, you don't need to enter info in to both.
Imagine if the speedometer and tach on your new sport bike showed the speed as 114.548240813 and the rpms as 12476.684507854. It's just cluttered confusing and unnecessary. Trying to do a quick glance for a reading is impossible, it's a crash waiting to happen
TM