Conversation
| /> | ||
| <div v-if="datatype=== 'number'"> | ||
| <v-radio-group | ||
| :value="editor.type" |
There was a problem hiding this comment.
Yup, editor probably needs to be checked to see if it exists, editor can be undefined.
| outlined | ||
| :step="editor.range[1]> 1 ? 1 : 0.01" | ||
| type="number" | ||
| label="Upper" |
There was a problem hiding this comment.
I would change label to 'Max'
| outlined | ||
| :step="editor.range[0]> 1 ? 1 : 0.01" | ||
| type="number" | ||
| label="Lower" |
There was a problem hiding this comment.
I would change label to 'Min'
| outlined | ||
| :step="editor.steps> 1 ? 1 : 0.01" | ||
| type="number" | ||
| label="Slider Resolution" |
There was a problem hiding this comment.
In would change label to something like 'Slider Step Interval' and the hint to something like 'Slider will increase/decrease by this value'
| :step="typeSettings.steps ? typeSettings.steps | ||
| : (typeSettings.range[1] - typeSettings.range[0])/2.0" |
| :min="typeSettings.range[0]" | ||
| :max="typeSettings.range[1]" |
There was a problem hiding this comment.
We either need to make the range required or have a default value
I think that's okay because I can't guarantee that the new range contains the old value. We auto set a range when they swap so that is why the value changes. Ideally this should be set up in the configuration file once and then values are undefined/0 until the user sets them on a specific track/detection attribute. |




editorobject which can include future visualization options for attributescoloroption for the attribute timeline/filtering toolsAttributesSlider.mp4