You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There's an assertion (jassert) in Debug mode when trying to inspect a comment name property with line breaks. The PropertyItemTextComponent's editor isn't set into multiline
To Reproduce
Steps to reproduce the behavior (in Debug mode)
Create a comment element (right-click on the graph panel, Add..., Add comment)
Type some multi-line text.
If you select this comment alone, a jassert is triggered when updating the inspector panel.
Expected behavior
I think the best thing to do would be to allow multi-line text property components. But that would need some visual trickery as the first line of the property's value would begin with the parameter's name label. e.g.
value: "This is a multiline
text looking good"
We would need either to add some 'offset' to the first line of the value's TextEditor, or
having smart connected editors for each line (that sounds heavy for objects that may have thousands of copies for a session) or, the simplest solution (but not as much satisfying) : just add a line break before the value section e.g.
value:
"This is a multiline text
made easy"
Desktop (please complete the following information):
OS: OSX 10.13.6
Version: 0.0.1
The text was updated successfully, but these errors were encountered:
Describe the bug
There's an assertion (jassert) in Debug mode when trying to inspect a comment name property with line breaks. The PropertyItemTextComponent's editor isn't set into multiline
To Reproduce
Steps to reproduce the behavior (in Debug mode)
Expected behavior
I think the best thing to do would be to allow multi-line text property components. But that would need some visual trickery as the first line of the property's value would begin with the parameter's name label. e.g.
value: "This is a multiline
text looking good"
We would need either to add some 'offset' to the first line of the value's TextEditor, or
having smart connected editors for each line (that sounds heavy for objects that may have thousands of copies for a session) or, the simplest solution (but not as much satisfying) : just add a line break before the value section e.g.
value:
"This is a multiline text
made easy"
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: