RadTreeview 2010Q2 ClientIDMode stuck in AutoID ?

[M]

Hi,

Does the RadTreeview in 2010.Q2 force AutoIDs now (and not allow us to Statically set IDs any longer as we could in Q1)?

With Q2, when I select a RadTree, then go to properties > ClientIDMode, it won't let me select anything other than AutoID.  (even though the other 4 choices appear (Inherit, AutoID, Predictable, and Static).  And now the Q2 Treeview also ignores my code-behind that was statically setting IDs to dynamically created RadComboBoxes.  (eg.)

...

 ddlItem.ClientIDMode = UI.ClientIDMode.Static
 ddlItem.ID = "ddlItem_" + strOrderDetailID

treenodeItem.Controls.Add(ddlItem)
 

This was working great in Q1, and would create an ID such as "ddlItem_12345",
but as soon as I upgraded to Q2, it was stuck in AutoID mode, and the controls
had "id="ctl00_ContentPlaceHolder1_RadTreeView2_i0_i0_ddlItem_12345" again (as it was before .net 4.0)

Am I missing some new setting?

Thanks,
Mike

[gunaah gunaah]

I have the same problem,

Can anyone provide solution for this problem.

thanks

[gunaah gunaah]

I have the same problem, styling a raddock and radzone.

Can anyone provide solution for this problem.

thanks

[Nikolay Tsenkov]

Hi guys,

Here is an article about ClientIdMode that you probably would like to read: http://www.west-wind.net/Weblog/posts/54760.aspx
This will give you a lot better idea about the ClientIdModes.

About the long generated ID's, you can fix this by placing your controls in a div-container and set the ClientIdMode of this container to static. This should cut the part of the id before this container.

Hope this is going to help you!


Regards,
Nikolay Tsenkov
the Telerik team

[rebtech]

great so your telling me i have to go through 20K plus lines of javascript and fix this in order to use the newest release.

[M]

uhh-oh...i just noticed that the radTextbox has the same problem.  (as in...I can't change it's property away from AutoID).

[Nikolay Tsenkov]

Hello,

I can confirm that the Q2 version forces AutoID as ClientIDMode. Our intention was only to make it the default value, but we also made it impossible to set another mode.

This has been fixed and ClientIDMode can be now set to different values. The change is part of the latest internal build that will be uploaded later today - 2010.2.727.

Apologies for the caused inconvenience.

Regards,
Nikolay Tsenkov
the Telerik team