RadScheduleView, custom Appointments and TimeZone grouping

3 posts, 1 answers
  1. Juanjo
    Juanjo avatar
    3 posts
    Member since:
    Nov 2012

    Posted 02 Jul 2013 Link to this post

    Hi there,

    In my project I have one implementation of RadScheduleView with custom appointments classes, which inherits from your IAppointment interface to show appointments into your control succesfully.

    Now I'm trying to implement a TimeZone grouping without success, ATM: The IAppontment TimeZone property in my class implementation returns a system time zone for all my appointments. 

    Then in my ViewModel I have a property TimeZonesSource (ObservableCollection<TimeZoneInfo>), which I've populated with my time zone I need to show.

    And then in my view, I have the group descriptor:

            <telerik:TimeZoneGroupDescription />

    When I run my project, I can see a group column for every appointment in my collection, and all appontments grouped in the last column (please see capture.png attached).

    I think something is broken / not implemented properly in my custom IAppointment class. Any ideas?

    Please help!

    Thank you and regards.
  2. Juanjo
    Juanjo avatar
    3 posts
    Member since:
    Nov 2012

    Posted 03 Jul 2013 Link to this post

    I've narrowed my problem.

    In my IAppointment implementation, in TimeZone property getter, if I return the timezone like this snippet, this strange behavior occurs:

    return TimeZoneInfo.FindSystemTimeZoneById("Romance Standard Time");

    But, If i return this in the getter, everything goes OK:

    return TimeZoneInfo.Local;

    This is very strange and have me totally blocked in this scenario, because I cannot use this Local value (I need to support two diferent time zones), and my program must be in use on both timezones.

    Please Help!


  3. Answer
    Konstantina avatar
    2332 posts

    Posted 05 Jul 2013 Link to this post

    Hi Juanjo,

    This sounds like a very strange problem.
    Could you please try to isolate it in a sample project and send it to us in a support ticket in order to debug it here locally. In that way we will be able to track down the source of the problem and provide a solution.

    Looking forward to your reply.

    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
Back to Top