Since adding RadDockLayout to my form, undesirable display features have been introduced

3 posts, 1 answers
  1. hkdave95
    hkdave95 avatar
    245 posts
    Member since:
    Nov 2006

    Posted 11 Aug 2008 Link to this post

    Hi

    Since adding a RadDockLayout to my masterform my page displays in a strange way.

    It gathers in the top left hand corner of the screen and then "explodes" into the full page.

    Please see an example at http://daresoft.no-ip.co.uk/dare-it.co.uk

    You will have to wait for the splash screen to finish before you can see the problem.

    Kind Regards

    David
  2. Sophy
    Admin
    Sophy avatar
    636 posts

    Posted 11 Aug 2008 Link to this post

    Hello,

    I opened the url you have sent us and received a javascript error - it is demonstrated in screenshot1. When I refreshed the page its content resized as shown in screeshot2. Is this the problem you observe or you mean a different behavior under "It gathers in the top left hand corner of the screen and then "explodes" into the full page."?
    The resizing process which is observed is due to RadSplitter calculating its size relatively to the browser window. If you do not want to observe the resizing process I could suggest you set the VisibleDuringInit property of the corresponding splitter to false in order to avoid the undesired effect which occurs while the page loads and the RadSplitter gets initialized.
    Please, describe in more details what is the behavior you observe when there is and when there isn't a RadDockLayout in your masterform and what is the behavior you expect.  

    Best regards,
    Sophy
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Answer
    hkdave95
    hkdave95 avatar
    245 posts
    Member since:
    Nov 2006

    Posted 11 Aug 2008 Link to this post

    Hi

    Thanks for the post.

    Sorry for my rather relaxed and undetailed post.

    However, you have got it right. It was the VisibleDuringInit  property that I was looking for to prevent the behaviour that was being exhibited.

    Kind Regards

    David
Back to Top