Instead of the control expanding vertically to accomodate all entries, they should be positioned on a single line.
Instead of having the property to select single or multiple it would be more productive to have a property called SelectCount and we can enter the amount of listings to be selected. If its a single I select 1... for multiple I select how many I need. No more need for the Single/Multiple property except for backward compatibility.
In your page http://www.telerik.com/help/aspnet-ajax/autocompletebox-onclientrequestfailed.html you only have one message to show to the user, why not return de http status code? In this moment the workaround suggested by your team is: <script> Telerik.Web.UI.WebServiceLoader.prototype._onWebServiceError = function (error, context) { var errorEventArgs = new Telerik.Web.UI.WebServiceLoaderErrorEventArgs(error.get_statusCode().toString(), context); this._raiseEvent("loadingError", errorEventArgs); } function OnClientRequestFailed(sender, args) { console.log(args.get_errorMessage()); } </script>
Based on customer feedback: there should be a property that limits the maximum height of the input of AutoCompleteBox. Once that height is reached, a scrollbar should appear.
It would be helpful if there was a built in way for a token to be a linked item. This could be done through an ItemTemplate or a NavigateURL property on an Entry.
RadAutoCompleteBox needs a Delay option to delay the retrieval of data while user is typing - in milliseconds.
When typing in a text control it would be nice to have auto-complete based on some predefined values. In my example we have a list of names setup against a handle like @johnsmith. If typing in the textbox when a person types a @name it would check against the available names and validate, if invalid they would be presented a list to pick the correct name (like how spell check works) This was brought up in a support ticket, notes below: Do have the following in mind: * implementing the simplest case e.g. @mentions will simply not do. there are tons of other completes that can be done e.g. #hashes, :emoji and so on * developers will need to verify that tokens are indeed valid and what to do with invalid tokens e.g. if I type @nosuchuser and there isn't such user, should the token be left literal or should it be processed like the rest? * there should be a way to specify the data source location for those completes... Perhaps more. But the most important part was the emphasis on the token validation and data source. Apart from that the logic is fairly simple: a textbox with events for keypress. As soon as a trigger key is pressed the autocomplete part pops and the user either selects a value from a list or types one. The "rich" value is saved in a hidden field. If the value happens to be a valid one, it has special formatting (because at the end we are submitting the rich value).
Occasionally, instead of a single request the controls will make multiple requests to the service.
Hi There, I do have a basic question regarding RadAutoCompletyeBox , the question is If the RadAutocompleteBox does not find the data that is typed to the text box what event will fire to say there is no data returned . Please can you guide me on this?