After working quite a bit with AjaxManager and ScriptManager I've gotten to love the Proxy additions of both controls as well as being able to easily get the current control when need be.
I thought the same would apply to ToolTipManager, however I was mistaken. Was there a reason this path was not taken when designing the component?
I checked the Page.Items collection and noticed ToolTipManager is not even added like both of the above mentioned controls. If you have any advice on using the Manager control on the root MasterPage and allowing the child pages to make use of it please share. I would hate to think I have to use some FindControl(), whenever I need access to it. That seems rather short-sighted.
Thanks,
Daniel
I thought the same would apply to ToolTipManager, however I was mistaken. Was there a reason this path was not taken when designing the component?
I checked the Page.Items collection and noticed ToolTipManager is not even added like both of the above mentioned controls. If you have any advice on using the Manager control on the root MasterPage and allowing the child pages to make use of it please share. I would hate to think I have to use some FindControl(), whenever I need access to it. That seems rather short-sighted.
Thanks,
Daniel