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

Refactor StateMachineInputs as DependencyObjects #1

Merged
merged 1 commit into from
Aug 8, 2022

Conversation

csmartdalton
Copy link
Collaborator

State machine inputs are not UI elements to layout, so we should use
[ContentAttribute] instead to implement them as light-weight
DependencyObjects.

Copy link
Contributor

@luigi-rosso luigi-rosso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice LGTM

Copy link

@michael-hawker michael-hawker left a 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.

RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/StateMachineInput.cs Outdated Show resolved Hide resolved
samples/StateMachineInputs/MainPage.xaml Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
samples/StateMachineInputs/MainPage.xaml Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/StateMachineInput.cs Outdated Show resolved Hide resolved
@csmartdalton csmartdalton force-pushed the contentattributes branch 2 times, most recently from 88910e0 to b6f1495 Compare August 5, 2022 01:42
Copy link
Collaborator Author

@csmartdalton csmartdalton left a 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.

RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
samples/StateMachineInputs/MainPage.xaml Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/StateMachineInput.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/RivePlayer.cs Outdated Show resolved Hide resolved
RiveSharp.Views.UWP/StateMachineInput.cs Outdated Show resolved Hide resolved
State machine inputs are not UI elements to layout, so we should use
[ContentAttribute] instead to implement them as light-weight
DependencyObjects.
@csmartdalton
Copy link
Collaborator Author

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!

@csmartdalton csmartdalton merged commit f48eea3 into main Aug 8, 2022
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

Successfully merging this pull request may close these issues.

5 participants