As for the secure frames: I see no reason this wouldn't work, though I haven't used them myself. tomQuest2 uses a custom CellProvider, and also supports quest items in the tooltip - your answer may lie there.
Just to clarify things, in tomQuest2 I'm not using secure frames for quests items in tooltip. I use the "WatchFrameItemButtonTemplate" template introduced in WOW 3.1, this template is not secured but can only be used for quests items as you just do a SetID(id) on your button where id is the quest id. (the OnClick is directly handled in the template).
Hmm. Just filed these as tickets so I don't forget.
Would you like that I upload some screenshots of both problems?
for the quest status hidden it should be easy to reproduce and make some screenshots, for the change of alpha it might take a little bit more time to reproduce.
another thing concerning colspan and minWidth / maxWidth.
When there is a colspan > 1 and minWidth, maxWidth parameters are defined in SetCell will minWidth and maxWidth apply to each columns of the colspan or is this for the global column.
for one line I have a SetCell for colspan = 2, minWidth = maxWidth = 370
will both column have minWidth = maxWidth = 370 or is it the total width of column1 and column2 that will be 370
Another thing is that I think that there is a padding of 6 between each Column so if I have another line with two setcell with colspan = 1 the total width of both columns should be 364 to include those 6 pixel padding. am I right?
(I'm currently working on improving the layout of achivements and quests tracker in tomQuest2)
I have a little problem with the scrolling part of LibQTip in tomQuest2. If I define my tracker as scrollable and open a quest category with lots of quests (more than that can fit in the tracker without scrolling) each quest status on the right of the tracker will be hidden, but if I scroll a little bit then the quest status will appear.
One other problem is sometimes for no reason the tracker content is almost translucent as if the alpha was changed.
I'll look into the height issue. As for the graphical corruption - that has to do with scaling the texture in the line. I've played around with it, and it seems you have to find a happy medium or you get artifacts. One size up or down can make them go away.
thanks for the info and for all you do for LibQTip
I have some strange layout in tomQuest2 with LibQTip.
How are the minWidth, maxWidth, lPad, rPad handled when doing a SetCell with a colSpan > 1 ?
It seems that for example if I do a SetCell with colSpan 2 and minWidth = maxWidth = 150 and the fontstring width of my text is greater than 150 it will split the text on two line, but later when doing the colSpan 2 the text will expand on two cell and only take one line but the cell will still have the height of two line. a screenshot of the problem will probably explain it better :
as you can see for quests without numbered objectives (white line objective) the height of the cell is too big. same thing for the zone "Ahn'kahet: The old kingdom" the text is not correctly aligned with the "+" texture to expand it.
So I think that there is a problem with the height computed by SetCell when colspan > 1 and we have a maxWidth.
Can you look into this problem.
I have another problem but I don't think that it's LibQTip related and only some people have this problem but I don't. I think that it's related to embeding texture in a fontstring, some people see some "|" between words when there is a texture embeded in the fontstring, if you look closely at the above screenshot you can see it.
maybe the best thing to do would be to test with tomQuest2, auditor and broker_factions together.
for tomQuest2 don't take it from svn, all locales files are generated by the packager even enUS.lua so you would have tons of errors (you could try with r128)