At present, when content arrives from one of the load-on-demand mechanisms in RadToolTipManager (AJAX request, web service, WCF web service), it is expected that it has static dimensions that match those set in the Width and Height property of the control. Having an autosizing feature similar to RadWindow's should let it update its size (e.g., height by provided width) and position according to the new content when it arrives. Samples are attached that showscase examples of resizing the tooltip once content arrives so you can use as base and implement similar resizing logic by calculating the dimensions of the content that came back.
No tooltip should be shown if there is no data for the tooltip: - RadToolTipManager: AutoTooltipify=true; IgnoreAltAttribute=true; no title attribute set for the elements on the page: no tooltips should be generated, but empty ones are - RadToolTip: IgnoreAltAttribute=true; no Text or content are set; no title attribute set on the target: no tooltip should be shown, but an empty one is Leave your comments below on the behavior you would expect from this property. Possible workarounds are attached to the thread.
When we have templates the generation of the clientIDs is dynamical. If some controls are removed and added back to the controls collection their clientIDs are changed. We can give a reference to the control in the Add method and onprerender the ToolTipManager could find their ClientIDs. E.g. the following demo: http://demos.telerik.com/aspnet-ajax/orgchart/examples/applicationscenarios/integrationwithradtooltip/defaultcs.aspx. is not working when we have DrillDown.
Many controls have items tooltip (RadComboBox, RadListBox, etc...) and every time is a pain to bind data in. You could implement support to "DataToolTipField" .....
The main wrapper of the tooltip is animated and the callout is positioned and shown after that. This makes it "pop" after the animation finishes. Disabling the shadow (EnableShadow=false) mitigates the effect somewhat. The callout can be positioned initially (if ShowCallout is not set to false) where it should be according to the Position property of the RadToolTip and its location can be updated at the end of the entire showing process again (as it is now).
There should be a method like GetRadWindowManager for RadToolTipManager called GetRadToolTipManager. This could be under the static $telerik.static library or as a global function that can be directly called without any prefixes. The goal is to find the RadToolTipManager in an easy and transparent manner in any content page, otherwise one needs to get the id from master page and then use $find, which is not an easy and transparent way of getting the manager object.
The error that is thrown on page load is that two components with the same ID cannot be added to the page. Possible workarounds: 1) set EnableAriaSupport to false 2) use client-side code to show tooltips, as shown in this demo: http://demos.telerik.com/aspnet-ajax/tooltip/examples/radtooltipmanagerclientapi/defaultcs.aspx .
The request needs to be encoded for the WCF service context to be able to recognize the data as a class the developer can create. A small sample is attached that: - overrides a function from RadToolTipManager to encode the request - has a simple WCF service implemented that shows how to access the passed data and use it