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
I have two issues that's related to -webide-representation
When we define type in external file(to use it with import in some other .ksy file) we have no way to use -webide-representation. Seems that obj, which passed to
have ksyType undefined on imported types.
2. I think we need more flexible way to represent values in -webide-representation. Especially numeric types. It would be nice to add the ability to limit the number of decimal places for float numbers. When we parse vectors, quaternions or matrices, this is especially desirable. Maybe in addition to hex, dec etc add len attribute, something like "{x:len=3} Or add more general dsl for value manipulations, like c format string or smth.
The text was updated successfully, but these errors were encountered:
Basically, the idea is to reuse existing KS expression language syntax, so we'd likely enhance KS expression language so it will include interpolated strings, rich formatting, etc.
I have two issues that's related to -webide-representation
have ksyType undefined on imported types.
2. I think we need more flexible way to represent values in -webide-representation. Especially numeric types. It would be nice to add the ability to limit the number of decimal places for float numbers. When we parse vectors, quaternions or matrices, this is especially desirable. Maybe in addition to hex, dec etc add len attribute, something like
"{x:len=3}
Or add more general dsl for value manipulations, like c format string or smth.The text was updated successfully, but these errors were encountered: