Actually, in my case, the setMethod null reference exception still helped me locate an error in my logic.
I was trying to set a property bound variable that had the following getter/setter:
1
get;protectedset;
In this case, I had to remove the “protected” keyword, for NodeCanvas to be able to set the variable correctly.
I still think a null check and extra LogError for that setMethod inside the catch {} block would be helpful, to hint to the user about potential cases like mine above.
Login
Register
By registering on this website you agree to our Privacy Policy.