TimeSlotCreated event raised before and after page load event

7 posts, 0 answers
  1. André Paradis
    André Paradis avatar
    1 posts
    Member since:
    May 2008

    Posted 20 Aug 2008 Link to this post

    Hi, during debugging with VS 2008 (Q2 2008 build 723) we remarked the following behavior:

    On the first request to the page, we have the page load event called, and then a series of TimeSlotCreated event raised.  Then if we cause a refresh of the scheduler using ajax  (we click on the day or week button on the ajaxified scheduler) , we notice that the TimeSlotCreated event are fired before the page load event, and then again after the page load event, which  caused us problems.

    We noticed this after upgrading from the future build  (708) to the release sp2 build (723).  In the future build, the TimeSlotCreated  event is always raised after the page load event.

    We can fix our problem, but i'd like to know why the behavior is different (set of TimeSlotCreated  raised twice in the latest build)

    Thanks
  2. Peter
    Admin
    Peter avatar
    6637 posts

    Posted 22 Aug 2008 Link to this post

    Hello André,

    Thank you for reporting this issue. We will fix it for the upcoming SP1 on August 26.


    Regards,
    Peter
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. Vijay
    Vijay avatar
    1 posts
    Member since:
    Jul 2011

    Posted 18 Jul 2011 Link to this post

    we have telerik version 2010.3.1317.35

    Timeslotcreated event fire before and after page load is solved or not?

  4. Peter
    Admin
    Peter avatar
    6637 posts

    Posted 20 Jul 2011 Link to this post

    Hi Vijay,

    You can check the release history - http://www.telerik.com/products/aspnet-ajax/whats-new/release-history/q3-2010-sp2-version-2010-3-1317.aspx

    Best wishes,
    Peter
    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!

  5. Kamalesh Patel
    Kamalesh Patel avatar
    5 posts
    Member since:
    Aug 2007

    Posted 21 Jul 2011 Link to this post

    Timeslotcreated event is called in page load before and after in the version 2010.3.1317.35.

    As per you told that for checking version history.  I have checked all version history listed (Please see attached image) but still there no any solution/fixed added in any version previously released.

    And you told this problem was solved on SP1 on August 26 on 2008.

    Then what i will do. Please give perfect solution and do not redirect any version history page or web service binding.
    Because we have very important coding in Timeslotcreated event.
  6. Kamalesh Patel
    Kamalesh Patel avatar
    5 posts
    Member since:
    Aug 2007

    Posted 21 Jul 2011 Link to this post

    Timeslotcreated event is called in page load before and after in the version 2010.3.1317.35.

    As per you told that for checking version history.  I have checked all version history listed (Please see attached image) but there no any solution/fixed added in any version previously released.

    And you told this problem was solved on SP1 on August 26 on 2008.

    Then what i will do. Please give perfect solution and do not redirect any version history page or web service binding or use of older versin control.

    Because we have very important coding in Timeslotcreated event.
  7. Plamen
    Admin
    Plamen avatar
    2933 posts

    Posted 22 Jul 2011 Link to this post

    Hi Kamalesh,

    I've already answered your bug report regarding the same issue and here is my answer:

    We have investigated deeply the problem you experience.
    And our investigation concludes that the behavior is expected.

    What happens there is:
     - 1 page lifecycle (initial load of the page) in which the Scheduler is initialized and timeslots are created;
     - response is sent to the client side;
     - at the client side the view is changed;
     - page lifecycle is triggered and executed in which:
        - the Scheduler is initialized and timeslots are created (the first execution of TimeSlotCreated handlers);
        - the post data coming from the client side is evaluated, viewstate is applied and the view is changed, which triggers reinitialization of the selected view;
        - with the new view, new timeslots are created (the second execution of TimeSlotCreated handlers).

    As you probably, see by now, this is like having a control in the aspx which is binded to a DataSource, and on PageLoad event binded to another (or even the same) DataSource - DataBound event will be fired twice.

    You will have to consider the possibility of running the handler for 2 (or more) different sets of timeslots (1 for each view that is selected).

    If you are experiencing difficulties in implementing this, please, feel free to contact us again - we will be happy to help you. If this will be the case, please, share a bit more details on what exactly do you need to execute on the TimeSlotCreated server event.

    Best wishes,
    Plamen Zdravkov
    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