SfSchedule v16.3.0.17-beta CellTapped event not fired when a selected cell is tapped

[John Prass]

I've needed to updated to 16.3.0.17-beta and after the update I have an issue where in DayView or WeekView (and probably others), when a cell is tapped and it is already selected, the CellTapped event will not be fired.  Is this a bug, or is there a different way to identify when a selected cell is tapped?

Also, I updated to the beta because I was running into this issue:

• #212293 - The NullReferenceException will no longer be thrown when removing the appointment after Schedule is launched and disappeared in NavigationPage.

Do you know if this fix will be rolled into 16.2 at any time?

Any help will be greatly appreciated.

[John Prass]

I've found a workaround for my issue.  I was creating a button when cell was selected covering the whole cell.  Apparently, before updating to 16.3 the celltapped event was falling through the button to the cell.  The functionality changed, but I'm not sure if it was an expected change or not.  I worked around the issue by adding a command handler to the button that is created when a cell is selected.

Thanks for a great product.

[Vigneshkumar Ramasamy]

Hi John Prass 

 

We have checked with your query. In SfSchedule, we have improved the TapGesture behavior when custom view is used schedule cell and appointment. You can handle the TapGesture between the schedule cell tap and custom view tap by using InputTransparency property of custom view. When InputTransparency is false custom view Tapped event will be triggered, otherwise schedule Tapped event will be triggered. Kindly refer the code snippet below,  

  

Code snippet:  

schedule.OnAppointmentLoadedEvent += Schedule_OnAppointmentLoadedEvent;

…  

public void Schedule_OnAppointmentLoadedEvent(object sender, AppointmentLoadedEventArgs e)  

{  

    var button = new Button()  

    {  

        BackgroundColor = Color.Blue,  

        VerticalOptions = LayoutOptions.FillAndExpand,  

        HorizontalOptions = LayoutOptions.FillAndExpand  

    };  

  

    button.Clicked += Button_Clicked;  

    button.InputTransparent = true;  

  

    e.view = button;  

}  

  

  

We have partially implemented this enhancement and included in our Volume 3 beta release (v16.3.0.17) which caused the break in existing behavior. We will include the complete implementation of this enhancement in our upcoming Volume 3 main release, which is expected to be available by next week of September 2018. We appreciate your patience until then.  

  

Regarding the “NullReferenceException” fix, this fix will not be rolled out in 16.2.x.x versions. If you require, we can include this fix in 16.2.x.x version and provide you custom assemblies. Can you please confirm the version for custom assemblies?   

  

Regards,  

Vigneshkumar R