It is important, from developer view, to have acces to all qTip callbacks described on the page http://craigsworks.com/projects/qtip/docs/api/#callbacks. I have some complicated actions inside menu minipanels, which should be handled by my own piece of code. Without access to qTip callbacks it is very hard (or impossible) to build custom behaviors. I will attach my proposal, soon.

Comments

kndr’s picture

Status: Active » Needs review
StatusFileSize
new3.78 KB

I am attaching the patch. Some modifications:

damienmckenna’s picture

Thanks for the patch, I've tweaked it a little, added some documentation and ported it to the D7 branch. I've tested this with both D6 and D7.

damienmckenna’s picture

Status: Needs review » Fixed

I've added the patches from #2 to both branches.

damienmckenna’s picture

StatusFileSize
new2.58 KB

The D7 patch needs this follow-on patch to work correctly.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

afmangum’s picture

Version: 6.x-1.2 » 7.x-1.0-rc2
Category: feature » bug

Looks like the module sets its own callbacks for certain events (beforeShow, beforeHide, onRender) which may cause problems since qTip 1 doesn't support multiple callbacks for events.