Hey ,
Thanks for that! I’ve had some of those points filed into proper feature requests and others as bug reports.
To clarify some of those odd functionalities:
[]
In coding, it is a common thing to have a class create an object member in its constructor.
After talking with some developers, I’ve learned that having a class create an object member in its constructor is not something that C++ does, so it won’t be something that can be done in Blueprints. That is a hard limitation unfortunately.
[]
Timelines are only possible in event graphs. Why cant functions or macros contain timelines. This would allow for simple animation functions instead of one messy graph
Timelines are latent functions that execute over a period of time/frames. They don’t work in standard functions because functions execute immediately, so they are something you can’t use there no matter what. Macros however, we’re looking into improving.
As for partial exposures, please let us know whenever you see anything like that. It’s unintended to limit anything like the example you used and we’d love to get them fixed up.
Thank you so much again! We really appreciate you being honest and giving all this constructive feedback 