After playing around with the stat creator device and some custom widgets, I’ve noticed a few things that would vastly improve the functionality and usability of this new device. Specific use cases for all of these can be provided upon request. These are in no particular order, some of them may be more applicable to MVVM in general, but ./shrug
- Exposal of the Z-order to be used for the widget that is actually being added to the viewport (to the device actors’ details panel)
- Addition of SetMaxValue and SetMaxLevel functions to the verse api
- Allow Conversion functions within MVVM sub-fields (currently they only seem to be allowed in primary/top level fields (for example, setting the text of a textblock allows us to directly reference the value of the stat creator device, but does not allow us to use a conversion function to apply some simple math to the value before conversion to text))
- Allow value to go negative (why is this clamped?)
- It appears as though the construction script of the actor for the stat creator device iterates in a loop for MaxLevel times, severe editor unresponsiveness when moving or pasting a stat creator device with a high maxLevel value (such as 999999)
- Addition of a DEB for increment value (for creators/users who are strictly in 1.0/creative)