I’m having a bit of trouble getting the default to actually be recognized. One would assume that setting the default to 1 in the following example would mean that if left blank by the user, the set_attribute in the render would utilize the default. Here’s an example:
That’s actually what I’m doing already to get around this.
But the docs say default is a universal control argument, so either:
It’s a bug and should be fixed
The docs are wrong and default is not universal
My understanding of default is incorrect (true, see below)
And thanks, unitless was only found on two element control docs so I didn’t even know about it. Although it seems to work either way for me. So I’m not sure what the benefit is?
Edit: I suppose my understanding of what “default” means could be skewed as well.
Yup, it turns out my understanding of default was incorrect. Default is just what is set automatically when creating a new element. If you clear it, it will be empty when accessing the settings object.
I feel it would be handy if the default was also passed along in the settings object, but I guess this isn’t exactly a bug and is more preferential.