Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-binding handler properties should also follow the path like binding properties do #21

Open
Brow71189 opened this issue Oct 28, 2019 · 2 comments

Comments

@Brow71189
Copy link
Contributor

For bindings, the declarative engine follows the "dotted path" of handler properties. Best example is using a PropertyModel where you bind to model.value. It would be great if this also worked for general handler properties that you are not binding to.

@cmeyer
Copy link
Collaborator

cmeyer commented Oct 28, 2019

Do you have a specific example of a widget and property specifier where this would be needed? Can you just use "@binding(path.to.property)"?

@Brow71189
Copy link
Contributor Author

For buttons with icons, I use a "IconManager" class. So the "path" to the icons would be UIHandler.IconManager.button_icon. Yes I am using @binding(IconManager.button_icon) and it works fine. I just thought it might be nicer to not use bindings where you don't need their actual functionality.
But it is not really an important change since binding works just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants