RootRadElement(s) appearing with weird names

2 posts, 0 answers
  1. Jure
    Jure avatar
    15 posts
    Member since:
    Aug 2008

    Posted 05 Feb 2009 Link to this post


    At some point I noticed three objects with names such as object_762c1357_1303_4649_ab06_ef217d90da91 in my class tree. I created a button to see which type they are (Me.lblTest.Text = Me.object_57d8c557_7ee1_4aa5_9b15_54ca310925ca.GetType.ToString()). They are of RootRadElement type. What is this?

    I safely deleted them in the Designer code. I do not want weird objects in my project that have no function. I'd like to know what they were if possible.

    I'm using Visual Studio 2005, 2.0, latest RadControls.

    Edit: Maybe it has something to do with RadControls disappearing from the toolbox earlier. I had to manually add them back.

    I also experience the following problem: in the RadGridView I try to "Edit UI elements". I change the font size in GridTableBodyElement->GridTableHeaderRowElement and click "Close". When I try to run the project I get an error in Application.Designer.vb:

     <Global.System.Diagnostics.DebuggerStepThroughAttribute()>  _
            Protected Overrides Sub OnCreateMainForm()
                Me.MainForm = Global.PM_Win._01_10_ProjectTreeStructure ' <- This line.
            End Sub

    The error says: An error occurred creating the form. See Exception.InnerException for details.  The error is: Index was out of range. Must be non-negative and less than the size of the collection.

    The I undo the changes in UI elements and it's ok.

    Sorry, maybe this edit should be in a separate thread.

  2. Nick
    Nick avatar
    767 posts

    Posted 09 Feb 2009 Link to this post

    Hi Jure,

    Thank you for your questions.

    Our guess is as good as yours - we have not seen such mystical objects, related to our controls before. Please, add our controls to the toolbox and try again.

    As to the themes, please use the Visual Style Builder when creating such for some of the dynamic elements in the grid. I have pasted an extract from a future article in our documentation about customizing RadGridView's appearance:

    There are four ways to customize RadGridView appearance - Themes, UI editor (DesignTime), Events, and Conditional Formatting. Each one has a field of applicability although they may overlap.


    Just as all our WinForms controls, RadGridView supports our theming mechanism. You can use one of the default themes or create your own theme. Please refer to our RadControls For WinForms Themes section in the documentation for more details.

    UI editor (DesignTime)

    Edit UI Elements can be started from the smart tag of the control. In particular for the RadGridView, it has a limited functionality so that row and cell properties cannot be edited. Cells and Rows are formatted using the other 3 approaches. Note also that there are no similar kind of limitations in Edit UI Elements dialog for the rest of our controls. The reason for this is that RadGridView employs UI virtualization and certain elements, for instance, cells are reused.

    Therefore, you can edit properties of other elements like GridTableElement and GridTableBodyElement. Actually these elements contain some properties that control behavior and appearance of grid cells and rows, like GridTableElement.RowHeight, RowSpacing and so on.

    Setting properties through Edit UI Elements dialog will override the corresponding values specified by the theme, which can be edited through the Visual Style Builder. On the other hand, if set through a theme, these property values will be distributed to RadGridView instances across the entire application for you to have more consistent look.


    Events are the most advanced way to edit cells and rows visual properties conditionally and unconditionally. Using events you can achieve everything that you can do with Conditional Formatting but the reverse is not true. The main advantage of Conditional Formatting is that formatting is set declaratively instead of procedurally as in the events approach. Please refer to the following two topics about row and cell events.  

    Conditional Formatting

    The main advantage of conditional formatting is the declarative approach used to describe formatting. It has limitations compared to events but also requires less code. Please refer to the following two section about cellsrows Conditional Formatting.

    Do not hesitate to write me back if you have more questions.

    Sincerely yours,
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Back to Top