Is it not possible to databind to the TimeLine /wo CodeBehind? I am not having any success without manually setting the dataSource in the LoadedEvent.
I built a list an exposed it in my ViewModel but the databinding doesn't happen. If I put a breakpoint in my Get accessor it never fires. Is this expected? Is this going to change? Bit of a pain.
I setup my XAML basically just like the demo...
<igtl:XamWebTimeline x:Name="timeline1" Loaded="timeline1_Loaded" > <igtl:XamWebTimeline.Axis> <igtl:DateTimeAxis ScrollPosition="0.55" ScrollScale=".45" /> </igtl:XamWebTimeline.Axis> <igtl:XamWebTimeline.Series> <igtl:DateTimeSeries DataMapping="Time=Time;Title=Title;Details=Details" DataSource="{Binding Path=MyProtocolScheduleList}" Title="My ProtocolSchedule"/> </igtl:XamWebTimeline.Series> </igtl:XamWebTimeline>
Until I added the following to CodeBehind the DataSource is null:
private void timeline1_Loaded(object sender, RoutedEventArgs e) { var timeline = sender as XamWebTimeline;
if (timeline != null) { timeline.Series[0].DataSource = ((MyEpmPageModel)Model).MyProtocolScheduleList; //timeline.Series[0].DataBind(); }
}
thanks
jack
http://community.infragistics.com/forums/p/60531/307504.aspx#307504
I am using Xamwebtimeline along with numerictimeaxis. Horizontal axis of the time line displays the unit as 1,10,20 etc (say unit is 10). Now I would like to display it as something like January, February, March...... on horizontal axis. How can I achieve this?
You can try adding the series to the visual tree.
private void XamWebTimeline_Loaded(object sender, RoutedEventArgs e)
{
foreach (Series series in this.Timeline.Series)
this.LayoutRoot.Children.Add(series);
With this the series will inherit the DataContext from the LayoutRoot.
Can I get around it with ElementBinding to set the DataContext to the parent?
I inherited version 9.1 from my old .NET + WPF package so I'm not eligible for the 9.2 upgrade.
Is there an ETA for that?
This is a bug. The DataContext of the series doesn't inherit from its parents. This is going to be fixed in version 9.2.