We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
INotifyPropertyChanged is lovely
INotifyPropertyChanged
But sometimes it feels like overkill.
I'd like to suggest adding an additional source binding interface - IRio - with a simple implementation Rio<T>
IRio
Rio<T>
In a ViewModel this could be written as:
public readonly IRio<string> FirstName = new Rio<string>("Initial value");
After this, then binding:
local:mvxBind="Text FirstName"
would be updated whenever the viewModel calls:
FirstName.Set("New value");
and anyone can get the value using
FirstName.Get();
(we might also be able to support cast operations - not sure)
Collections could be implemented using a Rio accessor to an INotifyCollectionChanged object.
IRio fields could also be mixed and matched with INotifyPropertyChanged methods too.
The name Rio is possible open to change...
Rio
The text was updated successfully, but these errors were encountered:
documented in video and N+1 sample now... as well as in wiki entry... so closing
Sorry, something went wrong.
No branches or pull requests
INotifyPropertyChanged
is lovelyBut sometimes it feels like overkill.
I'd like to suggest adding an additional source binding interface -
IRio
- with a simple implementationRio<T>
In a ViewModel this could be written as:
After this, then binding:
would be updated whenever the viewModel calls:
and anyone can get the value using
(we might also be able to support cast operations - not sure)
Collections could be implemented using a Rio accessor to an INotifyCollectionChanged object.
IRio
fields could also be mixed and matched with INotifyPropertyChanged methods too.The name
Rio
is possible open to change...The text was updated successfully, but these errors were encountered: