Apparently they are working actively on the scrollable branch, I'll try to do some test tonight in my internal build. From my understanding it should not be too complicated to add to tomQuest2 once it's part of the main library

Alyred: Concerning LibQTip and scrollbar in the LibQTip thread on the forum Tohral said one week ago "Actually, this is only feasible if the functionality is built into the core of the lib. Having said that, Elkano has made a scrollable branch under the LibQTip repository. I need to find some time (when my new CPU arrives...I"m on someone else's machine now) to look at it, but from a cursory glance it doesn't add much overhead to the code."

So I hope that it will be part of the library otherwise I'll have to check what I can do :)

I received this error while in the Argent Tournament area:
[2009/04/16 23:13:15-338-x1]: tomQuest2-110\questsTracker.lua:1312: attempt to call upvalue 'ChatEdit_InsertLink' (a nil value)

Also...just wanted to say thanks for the 3.1 update...and I just started to use the new quest-item macro and I love it already! Just another unique aspect of this addon that makes it one of the best available today. Thanks again Gagou!!

Disregard my previous report; seems there was some problem with the way it had loaded that time or a conflict with another addon that I've gotten resolved. Darn patch day.

At any rate, checked LibQTip and see they don't intend to add a scrollbar. Not sure if there is a function to limit maximum height for a box, but could it be done as an option (assuming this functionality exists) and if there are more quests than fit in the box, just have the user minimize some of the quests to get the display of what he or she wants? Or am I the only one who doesn't like boxes that grow uncontrollably? :)

The "Disappear when in combat" functions seem to work flawlessly; I am having some conflicts, however, with the built-in quest tracker. Keeps telling me that I'm out of space when I'm tracking quests, and to remove some before adding another. I'll see if I can narrow it down a bit for better debugging. It might have just been a one-time thing with the way it was loaded or something.