Odd behavior with ToolWindow and SchedulerNavigator

[Andy]

I hope someone can help me. I have a SchedulerNavigator contained inside a ToolWindow. When the ToolWindow is 'pinned' to stay visible, the Navigator's TimeZone changes to to Saskatchewan! This has caused some serious issues when loading appointments into the associated scheduler.

In addition, I have a radio button in the same container as the navigator that gets it's click event triggered when the window is 'pinned' as well. What events are triggered when the window is 'pinned'? I figure I need to start there.

[Andy]

Bump

[Ivan Todorov]

Hello Andrew,

Thank you for contacting us.

I was able to observe the described behavior. This appears to be an issue in RadSchedulerNavigator. I have logged it in our Public Issue Tracking System and we will address this in a future release. Here is the link to the PITS item: http://www.telerik.com/support/pits.aspx#/public/winforms/13365.

For the time being, you can use the following approach as a workaround. First, remove the association between RadScheduler and RadSchedulerNavigator at design time, then use the following code in your form's constructor to restore the association:

public Form1()
{
    InitializeComponent();

    this.radSchedulerNavigator1.BindingContext = new BindingContext();
    this.radSchedulerNavigator1.AssociatedScheduler = this.radScheduler1;
}

Your Telerik points have been updated. Feel free to ask if you have any other questions.

Regards,
Ivan Todorov
the Telerik team

[Andy]

Thank you so much! That works great. I don't suppose you could explain why that works could you?

[Ivan Todorov]

Hello,

The BindingContext in WinForms provides CurrencyManagers for the binding sources. In the common case, the BindingContext property of all controls is null and they get it from their parent control when they are added as a child (they do this until they reach a non-null BindingContext which is usually held by the form). This allows you to have different data controls (say a GridView and a ListView) bound to the same data source and having their current row synchronized. However, in the case where RadSchedulerNavigator is on an auto-hide tool window, it appears that its drop-down changes its BindingContext several times, which changes the current item. Most probably, this happens because the control is being re-parented. Fortunately, if you set explicitly a BindingContext to a control, it will not try to get if from its parents and this allows us to use this workaround.

Nevertheless, we need to investigate further the circumstances around this issue in order to make sure what causes it. We will try to address it a next release.

If you have any other questions, feel free to ask.

Kind regards,
Ivan Todorov
the Telerik team

[Andy]

Thanks for the insight.