is it common practice for programmers to go backwards when coding?
whats the point in defining a variable, and then putting it under a uproperty. if you know that a variable is going to need a uproperty, why the hell would you add that last? you were already on the line for the uproperty, yet you put something else there, just to have to move things down a line, to add the uproperty, when your cursor was already there.
Could you provide some context please?
It kind of is common practice to doing it this way as you would write your code with the least accessibility first and then only expose properties as and when needed.
It’s just that this is a tutorial so it is being done one step at a time. In a real project you would have written a whole bunch of C++ before considering what you want to expose to the Blueprint.
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.