AppointmentStartDragging event doesn't fire

[Unknown]

The AppointmentStartDragging event doesn't seem to fire when dragging appointments.  I have Syncfusion.SfSchedule.WPF46 installed through nuget.  The SfSchedule control is included in a user control as follows:

    <Grid>
        <syncfusion:SfSchedule x:Name="schedule" ScheduleType="Month"/>
    </Grid>

Just to test the event, the code behind includes the following:
        public CalendarView()
        {
            InitializeComponent();

            schedule.Appointments.Add(new ScheduleAppointment() { StartTime = new DateTime(2018, 6, 5, 5, 0, 0), EndTime = new DateTime(2018, 6, 5, 5, 30, 0), Subject = "Meet the doc", Location = "Hutchison road", AllDay = false });
            schedule.AppointmentStartDragging += Schedule_AppointmentStartDragging;
        }

        private void Schedule_AppointmentStartDragging(object sender, Syncfusion.UI.Xaml.Schedule.AppointmentStartDraggingEventArgs e)
        {
            throw new NotImplementedException();
        }

I have a breakpoint set at the beginning of the AppointmentStartDragging handler.  Whenever I drag and drop the appt, the event never fires (and the breakpoint is never hit), whether I am in Month, Day, or Week view.  I also tried this while binding the itemsource of the control to a collection of objects and using an appointment mapping.  In either event, the AppointmentStartDragging event never fires.

Any ideas why this event is not firing?

[Ganeshamoorthy Chandramoorthy]

Hi Kevin, 

 

We have checked with the provided information and we are able to reproduce the issue “AppointmentStartDragging event is not fired while dragging the appointment”. We have logged bug report for the same. We will fix this issue and include the fix in our upcoming Volume 2 SP1 release which is scheduled to be roll out at end of June 2018. We appreciate your patience until then. 

 

Regards, 

Ganeshamoorthy C 

[Unknown]

Great, thanks.  Kevin

[Ganeshamoorthy Chandramoorthy]

Hi Kevin, 

 

Thanks for the update. As we mentioned in previous update, we will fix the issue and include the fix in our upcoming Volume 2 SP1 release which is scheduled to be roll out at end of June 2018. We appreciate your patience until then. 

 

Regards, 

Ganeshamoorthy C