Nothing jumps out at me with the supplied code snippet. Is there a way
you can provide HTML, CSS and JavaScript either in a live page (or
isolated) that demonstrates the issue you are having?
Side notes:
- At first glance I don't see any reason to use anchorLinks.each() ...
using anchorLinks.cluetip() should iterate through all the
anchorLinks. In the code provided you're not using the 'i' parameter
for anything, so using .cluetip() should work just fine, no?
- The hoverIntent settings that you use may not have the intended
effect. Typically there is no reason to change the default interval or
sensitivity. I'd recommend keeping them at the default. But in case
you really want to change them, here's my lecture:
Setting the hoverIntent interval to 500ms means that every 500ms
hoverIntent will check the mouse position... which means your user
will have to wait 500ms at a minimum (or 1s, or 1.5s, or 2s...) for
the cluetip to appear. The purpose of hoverIntent is to not worry
about the delay, but instead open the cluetip when the user's mouse
slows/rests on the link (as fast as possible, but not before they show
intent).
Setting the hoverIntent sensitivity to 1 means that the user's mouse
will have to be completely motionless for the duration of your
interval. Typically you'd want to allow for some (small) motion
because not everyone has steady hands.
Anyhow, that's likely more than you bargained for and certainly not
what you were looking for. :) Let me know if you can provide a
complete set of code that demonstrates the issue.
Brian.
On Fri, Jun 5, 2009 at 4:41 PM, sduffer<shwetha.ga...@gmail.com> wrote:
>
> Hi Brian,
> Thanks for your reply.
> Here is the sample code i am using for jquery cluetip
> var anchorLinks = jQuery('.anchor-link');
> anchorLinks.each(function(i) {
> jQuery(this).cluetip({
> cluetipClass: 'rounded',
> dropShadow: false,
> positionBy: 'mouse',
> sticky: true,
> ajaxCache: false,
> arrows: true,
> waitImage:true,
> width: 300,
> closeText: 'x',
> hoverIntent: {
> sensitivity: 1,
> interval: 500,
> timeout: 0
> },
> mouseOutClose: true
>
> });
> });
> I am using each to have more than one cluetip on a page.
>
>
>
> On Jun 5, 1:08 pm, Brian Cherne <br...@cherne.net> wrote:
>> I exchanged a few messages with Renaud (aka LideIn), trying to get
>> sample code... but that effort stalled. I've got a busy weekend, but
>> if you supply some sample code or send me a URL (on or off-list) I'll
>> take a look early next week.
>>
>> Cheers,
>> Brian.
>>
>> On Fri, Jun 5, 2009 at 11:11 AM, sduffer<shwetha.ga...@gmail.com> wrote:
>>
>> > Did you get any clue to solve this issue. I am facing the same problem
>> > now
>>
>> > On May 17, 6:24 am, Lideln <lid...@gmail.com> wrote:
>> >> Hi,
>>
>> >> I have been using clueTip, and decided to use the hoverIntent feature.
>> >> Unfortunately, in some cases, the tooltip does not hide when I move
>> >> away from the element, and stays displayed forever.
>> >> It happens when I move quickly the mouse out of the element after a
>> >> very short delay (the tooltip is almost ending to fade in). Changing
>> >> the fade-in time does not correct the issue.
>>
>> >> For now, I have been forced to use a "max display time" for the
>> >> tooltip in order to quick-and-dirty fix that issue, but :
>> >> 1) it does not fix it entirely, because intead of displaying forever,
>> >> the tooltip stays displayed for a few seconds
>> >> 2) I can't let the tooltip displayed forever while the mouve is over
>> >> the element, which is sad for long tooltips
>>
>> >> Thanks for the help,
>>
>> >> Kind regards
>>
>>
>
