type-conversion in the UI

[bcristian]

Hello

Currently, the UI always assumes that conversions are made from variable to parameter.
But in the case of tasks that output data, the opposite conversion happens. And if such a mistake is made, a bunch of mysterious-looking errors will spew up, about missing variables and automatic promotion, because the setter cannot be found, which in turn causes the system to think it’s a dynamic variable which it tries to promote, but then “finds” it, the setter is still missing of course, and the cycle repeats at the next write, all the while everything looking ok in the UI, hence the confusion.

I suggest adding parameter direction attributes (in, out, both), so that the UI knowns what conversions to check for.

[bcristian]

off-topic, but related to type conversion, I suggest adding automatic Vector2 <> Vector3 (both ways) too. Already did it in my install 😀

[Gavalakis]

Hey,

Thanks for input. If a task parameter is marked as [BlackboardOnly] which is usually what OUT parameters should be marked with, then the UI will correctly show that the conversion is taking place (parameter -> variable). For all other parameters without [BlackboardOnly] attribute the conversion will be (variable -> parameter).
Basically the [BlackboardOnly] attribute kind of has the usage of an [Out] marker attribute, but I will investigate this further to see how it could be done better.

Sure. I will add Vector2 <-> Vector3 conversions in the next version as well 🙂
Thanks!

Join us on Discord: https://discord.gg/97q2Rjh

[Author]

Posts