Hey Telerik Team!

I am new to Telerik and trying to create a Popup that displays a RadGrid (which can be edited and added to). The Grid displays the Values that are in a RadComboBox, this should be used to add or change values.

My initial approach was to set up the RadGrid inside of a ToolTip, but I'm not sure if this is possible, or if it's a good solution at all. Is it possible to have the RagGrid use Ajax Postbacks while it's in the ToolTip or will the Tooltip close whenever there is a update to the Grid?

Is there a better solution to this problem?

Thank you for any suggestions,
Peter Ferak

The code for the example http://demos.telerik.com/aspnet-ajax/Window/Examples/CommunicationBetweenRadWindows/DefaultCS.aspx is incomplete in that it does not give the code for the window pages - in particular I am looking at how to generate the cityName and  seldate variables consumed by the parent page.

Thx

Hello. I create web form with Telerik controls. When this form is opened as modal dialog by follow code:


then crash in embedded script is occur.

Code causing crash:

Error message:
Not enough storage is available to complete this operation.

I think in popup windows javascript "navigator" object does not support "appVersion" property. How I can use Telerik controls in popup windows?

Hi

I get an error when I open a project in VS.2003 with telerik Q4 2006 for ASP.NET installed. All the telerik controls in the project is not rendered in the design view, instead they come with "Error Creating Control" red texts. This happened after I installed Q3 2008 in my computer, which I use in VS.2008 (it was not registered in VS.2003 - the Q4 2006 is still there). Is there a solution for my problem here? Can I re-register Q4 2006 just for VS.2003?

thanks

Regards
Pilu

I am using the Q3 2008 version of Telerik RadControls for ASP.NET AJAX treeview.  I want to do most of my add, move, delete and edit logic on the clientside, then when the user is done they hit a SAVE button and i'll persist the changes on the Server/DB.

This is working fine for add and remove.  But when I edit a node, no ClientOperation appears for this on the server side.  I should note I'm using a context menu for the edit and delete of nodes.

Some of my code:

The treeview .aspx



The Javascript for my EditNode method...

The code for the Remove works fine, removing the node from the screen and generating a remove operation type on the server.  The edit does not however generate the expected change operation.  The text of the edited node does change on the screen.  How to get this to work?

Hi

i have a raddatepicker using skin=webblue,  if user enter alphabetical  and special characters it is allowing  but it should not.
could anybody help

Very urgency ...

Thanks in advance

I have noticed that there are couple of ways through which we can increase the performance of the page.

1. This method is that we have noticed that the .axd files for each page are set for content expiration by Telerik itself, this is set for 1 year. So this will be downloaded again only when the page is requested for the first time.

2. This is manual method in which we can set the property EnableEmbeddedScripts="false", this will not load the JavaScript files from the assembly. The script reference will be needed for each JavaScript through the Script Manager for each controls. I tried this and it still loads one axd file of 119kb however we can explicity set the content expirtaion of the enitre script folder through IIS manager.

I see that the second method is beneficial because over the years I have noticed that setting the content expiration of JavaScript files works, however I am not sure how efficiently it works for the .axd files. Also, there are few JavaScript related to controls which are common for every controls like Core.js, Animation.js etc. The first method downloads the one axd file for each page, however if the second method is followed than the JavaScript file will be downloaded only once per control across the pages.

Would anyone know if it is beneficial to use the first option or the second option to increase the performance of the page?

Is it possible to have no restriction on the number of items per day in the MonthView. Right now you have to set it to a number and it will create more space for the additional items but I would like this to be a dynamic process so I dont have to limit the number of items per day using the MonthVisibleAppointmentsPerDay.

thanks,

chad

I have been trying to work with the Telerik controls.  I include the RadScriptManager at the top of every page and the page will run, but it is not combining the resource files.  I am using a tool to see the requests to the server and that is how I determined that the pages are not combining.

When I include the script I do it as shown here:

 <telerik:RadScriptManager ID="rscmScriptManager" runat="server"></telerik:RadScriptManager>

Then I add the reference to the Web.config file as shown here:

 

<

 

add path="Telerik.Web.UI.WebResource.axd" verb="*" type="Telerik.Web.UI.WebResource, Telerik.Web.UI" validate="false"/>

Please help me to figure out what I have done wrong.  I have searched quite a bit for articles online, with no success.

Regards,
Cynthia

 

 

 

 

 

 

 

 

 

We just bought the Telerik suite of controls mainly because we needed a speller and the free ones had some issues.  So we assumed a pay one would be relatively bug free.
Unfortunately, the Telerik one has just as many issues, maybe worse ones.
We found that if you have fixed size spell checking area, the text overflows the boundaries when the control is disabled.
We also found the spell checker to be unusable if you have a control in a page which is several screens long.
The browser window scrolls  around and hides the text every time it finds a misspelled word.
Both of these behaviors are observable on the Telerik demo page if you put in a lot of text.

I was wondering if the community feels that the Telerik controls (speller and others) are ready for use in a production environment?

We found a work around for the first issue but the second one won't be fixed until the next quarterly release.  This leaves us in a bad way because their is no way I would torture a user with the browser scrolling issue.