On Nov 18, 2007, at 8:23 PM, Rick Faircloth wrote:
Hi, Karl…
The plug-in is working much better now that you implemented the
various positioning features. I went back to auto to check out the
cluetip image behavior and, you’re right, ‘auto’ works better for
me than ‘mouse’.
thanks! and glad to hear it.
The problem I was having with a setting of “positionBy: ‘mouse’” is
that the pop-up image in the ClueTip would overlap the photo in the
page that is being moused over to trigger the ClueTip. If I moved
my mouse fairly quickly over the trigger image too far from the
right or left, the ClueTip image wouldn’t show. Using ‘auto’
places the ClueTip off the trigger image and eliminates that problem.
The only issue I have with the ‘auto’ setting is when only the very
bottom of the trigger image is showing at the top of the browser
window, then the ClueTip image doesn’t move down far enough into
the window. It remains partly cut off at the top because it will
only re-position itself downwards only so far, and then no more.
This is not a big problem, since all I have to do is scroll the
trigger image down into the page, and then I can see the full
ClueTip image. The re-positioning behavior works well on the
bottom of the browser window.
I think I'll have to see these to be able to fix them. I appreciate
the description of the problem, and I kind of understand what's going
on, but I'm helpless sometimes without the visual aids. ;-)
Sorry I don’t have a site for you to view this behavior on. The
site is still on my local workstation. I’ll be putting it onto the
server for the site owner in the next couple of days and I’ll let
you know where to view the plug-in at work.
No problem at all. Just let me know when it's available for me to
poke around with so I can get it working better for you.
It’s a great plug-in and I use it on almost every site I’ve developed.
thanks again. :-)
Oh, and one more thing… the quote issue wasn’t a matter of double
vs single quotes, it was a matter of “no quote” vs single quotes.
At first I didn’t have any quotes around auto, which wasn’t
working. I noticed that some of the attribute values had quotes,
so I decided to put the quotes on and make it ‘auto’ and it worked.
Ah ha! That sounds more reasonable. All of the option values that are
strings must have quotes (though the "keys" don't need them, of
course). Some of the other options are integers or booleans, which
don't take quotes. This is true of any object literal in JavaScript.
Glad there wasn't something really strange going on with single vs.
double quotes. That would have been freaky.
Cheers,
Karl
