The unbound (virtual mode) datagrid is useful when...
#1 your data type don't support notification such as INotifyPropertyChanged
and you can't change the data type to do so...
#2 your data is itself synthetic, created as the result of some calculation
rather than the result of concrete data items in a data object someplace.
#3 you have very fast realtime data and do not want the notification
mechanism to refresh the grid every time it's updated. In this manner you
can control and throttle the update speed of the grid to limit processor
usage due to excessive paint cycles.
to name but three that strike me immediately. I'm sure thare are other good
reasons.
--
--
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.
"TonyJ" <jo*****************@telia.comwrote in message
news:Ou**************@TK2MSFTNGP03.phx.gbl...
Hello!
I just wonder when is it necessary to use unbound datagrid. It's far
simpler
to use databound datagrid by using the wizard.
Can you just point on some particularly example when an unbound datagrid
would be suitable.
//Tony