Ajax call not being made from qtip

[sz3y1w]

Hi,

first time I've used qtip and it looks like a terrific plug-in. I am looking to update the content of a hover-over with content from an ajax call, but I am having trouble contacting the server.
I have some images in a grid with their onClick() set to fire the following function that I've pieced together this from the demos -

JS Code

function registerHoverOver() {
$('.ApplyHover').qtip({
            content: {
                text: 'Loading...',
                hide: 'mouseout',
                solo: true,
                ajax: {
                       type: "POST",
                       url: "MyPage.aspx/MyWebMethod",
                       data: "{}",
                       contentType: "application/json; charset=utf-8",
                       dataType: "json",
                       success: function (data) { return data.d }
                      }
            }
        })
}

All I get is the "Loading..." text. I've checked in Firebug and there's no errors in the console, Fiddler doesn't show any traffic off it at all and debugging MyWebMethod doesn't get hit . If I make an Ajax call in a separate function -

JS Code

function registerHoverOver() {
$('.ApplyHover').qtip({
            content: {
                text: 'Loading...',
                hide: 'mouseout',
                solo: true,
                ajax: doAjax()
            }
        })
}
 
function doAjax() {
        $.ajax({
            type: "POST",
            url: "MyPage.aspx/MyWebMethod",
            contentType: "application/json; charset=utf-8",
            data: "{}",
            dataType: "json",
            success: function (data) { var x = data.d  }
        })
    }

then I do get data back the way I would expect it, but I can't get it into my qtip content. Where am I going wrong with this?

Many thanks in advance for any replies.

[Craig]

I wouldn't bind qTips on mouseover without setting overwrite to false if I were ,you otherwise ,you'll end up spawning a new qTip for every mouse over, even on the same element. Is there a reason you're not just applying them on document ready?