-
Notifications
You must be signed in to change notification settings - Fork 7
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
Refactor StateMachineInputs as DependencyObjects #1
Conversation
84daac7
to
8bca39f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, left some more architectural notes on how XAML works. Some things may be good quick things to fix now, others you may want to leave as TO DOs.
88910e0
to
b6f1495
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for the detailed feedback. This is looking better and better.
State machine inputs are not UI elements to layout, so we should use [ContentAttribute] instead to implement them as light-weight DependencyObjects.
b6f1495
to
efec6a0
Compare
Looks like all the feedback is addressed, except the properties stuff. I'll put that together in a new PR and go forward with landing this one! |
State machine inputs are not UI elements to layout, so we should use
[ContentAttribute] instead to implement them as light-weight
DependencyObjects.