RadTextBox disappeared after anchoring

6 posts, 0 answers
  1. DGPunkt
    DGPunkt avatar
    20 posts
    Member since:
    Apr 2007

    Posted 08 Dec 2009 Link to this post

    Hello everybody,

    has anyone tried to anchor a RadTextBox top, bottom and right (Q3 SP1)??

    Using the Designer View:
    I just have a Form, drop a RadTextBox onto that Form, anchor the RadTextBox top, bottom and right and when I start the application I just see the Form. There´s no RadTextBox.

    Greetings,
    Daniel
  2. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 09 Dec 2009 Link to this post

    Hi DGPunkt,

    Thank you for reporting this, your Telerik points have been updated.

    You can go around this issue by setting the Anchor property after InitializeComponent() method in your Form constructor. However, before doing so, you must set the AutoSize property of RadTextBox to false.


    Regards,
    Victor
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. UI for WinForms is Visual Studio 2017 Ready
  4. DGPunkt
    DGPunkt avatar
    20 posts
    Member since:
    Apr 2007

    Posted 18 Dec 2009 Link to this post

    Hello Victor,

    I just started (again) using Q3 SP1 and remembered something with AutoSize property but I didn´t find it in designerview. Did you make AutoSize property of RadTextBoxes invisible in designerview or is it just a bug :) ??

    Greetings,
    Daniel
  5. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 19 Dec 2009 Link to this post

    Hi DGPunkt,

    AutoSize is not a valid property of a text box control since it implies that the the text box will be resized if the text length changes. This behavior is accommodated by MultiLine property instead. We intentionally hid the property at Design Time and we will also hide it at Run Time in the next release. It will still work and be available but it won't be visible in the intellisense so that its use will be discouraged. Please write again if you have other questions.

    Kind regards,
    Victor
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  6. DGPunkt
    DGPunkt avatar
    20 posts
    Member since:
    Apr 2007

    Posted 21 Dec 2009 Link to this post

    Hi Victor,

    did you read your post from Dec 9??

    There you told me about setting AutoSize property for RadTextBox to false AND
    if I don´t set it to false I get those problems with width of RadTextBoxes (Docking Left, Top, Right) inside a RadPanel inside a TableLayoutPanel with 3 columns set 33% inside an UserControl inside a (Rad-)TabPanel inside CAB Framework. :)

    We wonder that it is very difficult for us to build a sample application, because in a plain normal form most RadControls work fine...

    What I found out is, when we start our application, the textboxes parents width is set to 1px for a moment and then set to its "normal" size. The textboxes width results in 0px and then - as far as I remember - to parents width - 1px...


    Have a nice Christimas.
    Greetings from Berlin, Germany

    Daniel

  7. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 23 Dec 2009 Link to this post

    Hi DGPunkt,

    I am afraid I did not fully understood your last post. I read the post and it still makes sense. We simply have to fix the anchoring issue on our side and the users will not need to bother themselves with AutoSize property.

    AutoSize is a really special property in the text box case. It is being respected in the layout but should generally not be used in other scenarios.

    Please write again if you have questions about our controls.

    Sincerely yours,

    Victor
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Back to Top
UI for WinForms is Visual Studio 2017 Ready