local tooltip = LibQTip:Acquire("ToolTipName")
-- code to fill tooltip here
The tootip will auto-hide shortly after leaving, so no OnLeave (or an empty function dummy) is needed for the data object.
Yeah, we are aware of that 'bug' for some time now. The 'funny' thing is that re-setting the tooltips content sometimes also fixes the issue so maybe it's a bug in Blizzard's code for calculating the width of fontstrings.
I think if you had used topleftRow, topleftColumn, bottomrightRow, bottomrightColumn
instead of topleftX, topleftY, bottomrightX, bottomrightY
it would have been more clear ^^
Shouldn't be that hard, too. Instead of coloring the cell/column/row frames one would use an additional layer of frames that would be anchored to the columns/rows as needed.
Only problem would be that you'd have to know how many lines the tooltip has to reproduce the column function.
it expects a function, not a string pointing to a member of your addon object.
local function tooltipOnClick(creatureSlotID, ...)
local y, x = IPMount.tooltip:AddLine();
IPMount.tooltip:SetCell(y, 1, sName);
moved most of the LibQTipClick functionality into LibQTip itself (though with different code)
new API (script is OnEnter/OnLeave/OnMouseDown/OnMouseUp, function will be called as frame:function(argument, ...)):
- SetCellScript(line, column, script, function, argument)
- SetLineScript(line, script, function, argument)
- SetColumnScript(column, script, function, argument)
Feel free to enjoy :) Torhal already facepalmed over his LQC work ;)
and even if there are, which is not, they would be comiting suicide... ähm... they would just sit inaccessable in the old heaps resulting in a bit memory overhead but nothing breaking. Since they only get into the heaps when no longer being used.
And wrt the exposed functions: as you said, they never were part of the API so I don#t see any problem in breaking them.
6) You mouse over Broker_Factions again. (I think) a new LibQTip tooltip gets acquired. It's lines are cut (suffixed with ".....") and the orientation is borked.
If all the long lines in each column used to be trunkated with ... then this error should be fixed. It was caused by scaling the tooltip. For some reasons, some of the internal frames weren't correctly anchored and thus kept the wrong scale.