Default parameter syntax?

Emily_Qi_Wang

What is the syntax for setting default parameter values when defining a new feature?

I checked the doc files and SCOPE Weds slides that Kevin sent recently and didn't see this mentioned; apologies in advance if it's obvious and I missed it.

===

Code excerpt example (Also, are there code blocks in the Onshape forum discussion editor?)...

    precondition

    {

        annotation { "Name" : "Radius" }

        isLength(definition.radius, LENGTH_BOUNDS);

        annotation { "Name" : "Teeth" }

        isInteger(definition.teeth, POSITIVE_COUNT_BOUNDS);

    }

    // function action stuff here //

    { /* default parameters can go here?? */ });

===

For the default parameters block, I tried a few things:
* "definition.teeth" : 10
* definition.teeth = 10
* "Teeth" : 10 
* and so on...

Thanks in advance!

john_f_carr

The default is a map, so { teeth : 10 } should do it.  Also { 'teeth' : 10 }.  We have code blocks. Switch to HTML mode with the slash-in-angle-brackets icon and use code.../code around your code block.

john_f_carr

On second thought, I'm not sure if that makes the UI see the default. It makes the feature use 10 if teeth is undefined. That's not quite the same as putting 10 into the feature dialog.

john_f_carr

Try a Default annotation. You'll find them in std scattered around. For example, in boolean.fs annotation { "Name" : "Merge with all", "Default" : false } booleanDefinition.defaultScope is boolean; Default works for string, boolean, and enum. It doesn't work for number. I doubt there is a strong reason for it not working for number. Somebody needs to write the code. Maybe we'll get a feature request...

ilya_baran

@john_f_carr The reason it does not work with quantities is because the defaults usually depend on the units, hence the valueBounds mechanism. isAnything (which is intended to let the feature user enter an arbitrary expression, though it's somewhat limited currently) is the one thing missing the default mechanism.

In this case, the thing to do is to make a local copy of POSITIVE_COUNT_BOUNDS from valueBounds.fs and adjust the middle number (the default).