Referencing blueprint widget elements that aren't variables
Hello, Im trying to add a version of the BPW_Production display widget to my widget. Long story short... Im at the bottom of the stack trying to figure out how to access input items. I noticed that if I make an instance of BPW_Producion_Display_Module_InputOutput, I cannot access mcontent. However if I make a new blueprint that inherits UserWidget, and copy over everything from BPW_Produciton_DisplayModule_InputOutput, I can access that canvas no problem. The only difference between the two would be that BPW's inherits BPW Production Display Module, and then UserWidget. Why might I be able to access mcontent one way but not the other?
Solution:Jump to solution
if it isn't a variable you can either make it one yourself in your local copy of the editor (works, but not a good idea because it will break every time the content folder updates) or get a reference to it on widget (pre) construct by jumping parent/child from something that is a variable @MrWolf
3 Replies
by "access" I assume you are referring to "have a node that references it in blueprint code"
this is controlled at editor time by a checkbox in the widget designer that controls if the element is a variable or not, I don't remember the exact label on it
Solution
if it isn't a variable you can either make it one yourself in your local copy of the editor (works, but not a good idea because it will break every time the content folder updates) or get a reference to it on widget (pre) construct by jumping parent/child from something that is a variable @MrWolf
This worked, thanks robb