Search Issue Tracker
By Design
By Design in 2.2.X
Votes
0
Found in [Package]
2.1.0
2.2.0
2.2.1
Issue ID
SPLB-200
Regression
No
Spline Overlay Element Inspector has cut off values when the entered values are longer
How to reproduce:
1. Open any project with Splines installed
2. In Scene Hierarchy create a Spline > Draw Spline Tool
3. Draw a couple of Knots
4. Reenter the tool and select a Knot
5. Enter a long value and see its scientific notation
Actual result: The Overlay menu cuts off some of the Z value
Expected result: The Overlay menu either expands for the whole scientific notation to be readable
Reproducible with: 2.4.0 (2021.3.31f1, 2022.3.11f, 2023.1.16f1, 2023.2.0b14, 2023.3.0a9)
Reproduced on: Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
However, we know each case is different, so do please continue to log any issues you find, as well as provide general feedback on our roadmap page to help us prioritize.
Resolution Note (2.2.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
However, we know each case is different, so do please continue to log any issues you find, as well as provide general feedback on our roadmap page to help us prioritize.