Can't access Widget Component properties in BP code

Development Programming & Scripting UI
, , , ,
1

It’s possible to set this properties via Details panel (inside component and on it’s instance).
But it’s not even possible to even this properties in blueprint version of this component. And that’s prevents from using these properties in my custom code… :frowning:

Please check attached image :wink:

2

You can get/set them like this:

3

Nope, that returns you constructed widget :wink:

What I need is access to properties of Widget Component which is used to attach UI widgets to actors in world :slight_smile:

4

What do you need to access if I might ask? The Important stuff is exposed. Aside from that nothing is marked Private in C++ so you could easily create a couple Functions in a extend class that you can access from BP. I did not look at the Init or Update functionality so I asume changing the unexposed stuff at runtime will have no effect (check that part yourself ;P)

5

Hey kjustynski-

Which properties are you referring to in your screenshot? If you’re trying to set the Widget Class from code you can use the SetWidget() function. Providing more information about what you’re trying to accomplish will also help in finding a solution that works.

6

Hey, I’m sorry for lack of details in OP :wink:
I can access only Draw Size property. Can’t directly access anything else in User Interface and Interaction categories.
The reason I need this, I’m building kind of wrapper for Widget Component to speed up work. My entire plugin is all about decrease time needed to implement UIs.

So it’s sometimes useful to native property and call next actions based on additional params. Currently I can’t even Widget Class for this component from Widget Component properties - needed to duplicate this param in my “wrapper” and then I can default values of widget class, etc.

7

Yeah, I could write few simple functions for that. But…

I’m working on plugin that speeds up UI implementation. It’s mostly about expanding functionality of native UI elements. Few more params, not too much code and… lot of boilerplate reduced. Faster to create UIs.
I’ve decided most of the plugin in BP, it would much more accessible for users. They could modify/improve for their projects if needed.

And there are very few cases where I can’t access something in BP :slight_smile:
Actually dev team exposes few missing things in every release. It would nice to expose these properties too :slight_smile:

8

Hey kjustynski-

I have entered a feature request to make the properties of the User Interface section of the widget component accessible with Get/Set functions. You can follow this report here: Unreal Engine Issues and Bug Tracker (UE-45371) . You can track the status of the request as it is reviewed by our development staff. Please be aware that this request may not be implemented, or that it may not be prioritized to occur anytime soon.

Cheers

9

Is there any particular reason the referenced issue doesn’t exist?

10

Hey Whimsy-

The linked issue is not on the public tracker because it was entered as a feature request, and we want to keep the public tracker limited to bugs only. The reported issue is currently unresolved and open for consideration into the engine.