Strange behaviour of appointment events

2 posts, 0 answers
  1. Hardik
    Hardik avatar
    61 posts
    Member since:
    Jun 2011

    Posted 12 Jul 2011 Link to this post

    Hi support,

    In my application there are different types of users, Some can only see the scheudulerView not any transaction(Edit,Update,Delete) can be possible. Some users can only create appointment, some can only modify the appointment.

    So As per my requirement I have done coding. A user whom have only read permission, I make all slots readonly. So he can't create any appointment. But at the same time that user can double click the  appointment and see the details of that appointment, but not able to modify. So in edit appointment dialog as per user permission all fields are disable. User can only see the appointments details.

    I have found very strange behaviors of appointment events.

    An appointment in simple slots(not readonly)

    When I double click on appointment at that time following events called.
    1.XamlRadScheduler_AppointmentEditing
    2.XamlRadScheduler_ShowDialog
    3.XamlRadScheduler_AppointmentEdited
    This is right.

    Strange behavior.(An appointment in readonly slot)
    When I double click on appointment at that time following events called.
    1.XamlRadScheduler_AppointmentEditing
    2.XamlRadScheduler_ShowDialog

    The event  XamlRadScheduler_AppointmentEdited is not called. When I again double click the appointment then  XamlRadScheduler_AppointmentEdited  called. then again

    1.XamlRadScheduler_AppointmentEditing
    2.XamlRadScheduler_ShowDialog
      and stop. Again double click then same as above.

    Because of that logic done in edited event not execute  and its make a problem for me.

    Is there any solution for that? Or its bug. Can you give any suggestion that editing and edited behavior same as in simple mode

    Thanks
    H@rdik Pancholi
  2. Valeri Hristov
    Admin
    Valeri Hristov avatar
    2252 posts

    Posted 15 Jul 2011 Link to this post

    Hi Hardik,

    When the Edit Appointment dialog is opened the corresponding appointment is put in edit mode, regardless of it being read-only or not. When you are closing the dialog, if the appointment is read-only, the edit is cancelled, hence there is no Edited event (because there was no editing). This is the expected behavior.

    Why do you need to use the AppointmentEditing/Edited events?

    Regards,
    Valeri Hristov
    the Telerik team

    Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!

Back to Top