Databinding has existed since the first version of .Net.
PropertyGrid isn't a true databound control in the same sense that
DataGridView is for example.
As a consequence it doesn't use the INotifyPropertyChanged or
<property>Changed events exposed by various objects.
PropertyGrid needs to be refreshed when you make a change to an object
externally. You can subscribe to the INotifyPropertyChanged or
<property>Changed yourself and just refresh the property grid.
--
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
[quoted text, click to view] "Cartoper" <cartoper@gmail.com> wrote in message
news:94ce8c94-6f1d-4f8d-af9c-a3a0c192631c@x41g2000hsb.googlegroups.com...
>I have used data binding in .Net 2.0 and love it, from what I
> understand what I used in 2.0 was new. Today I am working with .Net
> 1.1 and wondering how to wire things up correctly...
>
> There is a PropertyGrid that has had it's SelectedObject set to a data
> class. From time to time the values of this selected object will
> change outside of the PropertyGrid. What needs to be wired in so the
> PropertyGrid knows when the values change in the data class?