mtsu_bravo Posted October 23, 2007 Report Share Posted October 23, 2007 I think I found a bug, below is a test case. Public Class test Private _age As Nullable(Of Integer) Private _date As DateTime = Date.Now Public Property age() As Nullable(Of Integer) Get age = _age End Get Set(ByVal Value As Nullable(Of Integer)) _age = Value End Set End Property Public Property dateNow() As DateTime Get dateNow = _date End Get Set(ByVal Value As DateTime) _date = Value End Set End Property End Class Dim testList As IList(Of test) = New List(Of test) Dim test1 As test = New test Dim test2 As test = New test Dim test3 As test = New test test1.age = 14 testList.Add(test1) test2.age = 15 testList.Add(test2) test3.age = 34 testList.Add(test3) Chart1.DataSource = testList Chart1.DataBind() any time I have a property with a type of nullable it just puts in zeros for the values. I saw some other posts were they had similar problems but were not using list objects. Quote Link to comment Share on other sites More sharing options...
Frank Posted October 24, 2007 Report Share Posted October 24, 2007 Nullable objects are currently not supported when binding to CLR objects. You need to use the Data API to pass these values as Chart.Hidden. Quote Link to comment Share on other sites More sharing options...
mtsu_bravo Posted October 31, 2007 Author Report Share Posted October 31, 2007 Can you point me to the "Data API" documentation or provide me with an example of changing the example above to what you are refering to? Quote Link to comment Share on other sites More sharing options...
Frank Posted October 31, 2007 Report Share Posted October 31, 2007 The documentation is part of the API documentatation. Inside the Chart Object, go to the Data property: http://support.softwarefx.com/OnlineDoc/CfxNet70//WinAPI/Chart_Data.htm A sample app can be found at: http://support.softwarefx.com/Samples/CfxNet70//Samples/PassingData/Default.aspx The option you are interested in is API. Quote Link to comment Share on other sites More sharing options...
zac morris Posted March 14, 2008 Report Share Posted March 14, 2008 Will this behavior be fixed in v8? The increasing prevalence of nullable types in newer data access APIs (LINQ to SQL, Entity Framework) makes this shortcoming a pain. Thanks, Zac Quote Link to comment Share on other sites More sharing options...
Frank Posted March 14, 2008 Report Share Posted March 14, 2008 Integration with these new technologies is in the works. Quote Link to comment Share on other sites More sharing options...
cbg3 Posted May 2, 2008 Report Share Posted May 2, 2008 +1 for nullable type support. --Ben Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.