Quantcast

TooltipMain and ChatFrame1 are tied together in terms of intersect checks. LibWidget will watch whenever StarTipTooltipMain and ChatFrame1 intersect. What happens is the StarTipTooltipMain is hidden with alpha=0. It's a round about way of fixing the issue while mousing over the ChatFrame1 and there happens to be a unit right behind it. Before the tooltip hid all the text on ChatFrame1, and I guess the only way to get rid of it was to use an inverted modifier key and physically hide the tooltip that way. Note the default rate should be pretty slow. The current 500ms is way too fast for something rarely checked. Maybe once a second. There's also the possibility of creating a MouseGesture using ChatFrame1 as, and configure it so when you simply click on ChatFrame1 then StarTipTooltipMain hides. hmm

Author Scott Sibley <sisibley@gmail.com>
Author date 2011-07-30 10:16:00
Author local date 2011-07-30 05:16:00 -0500
Committer Scott Sibley <sisibley@gmail.com>
Committer date 2011-07-30 10:16:00
Committer local date 2011-07-30 05:16:00 -0500
Commit 1a2eab1a9196e88b94149664ad64d2f1619c685e
Tree 4991418f85c9373e13eda08c6d0e3cb80381f831
Parent 8cea4c1ce14fbba0547b90897eda53a1d8d44701
TooltipMain and ChatFrame1 are tied together in terms of intersect checks. LibWidget will watch whenever StarTipTooltipMain and ChatFrame1 intersect. What happens is the StarTipTooltipMain is hidden with alpha=0. It's a round about way of fixing the issue while mousing over the ChatFrame1 and there happens to be a unit right behind it. Before the tooltip hid all the text on ChatFrame1, and I guess the only way to get rid of it was to use an inverted modifier key and physically hide the tooltip that way. Note the default rate should be pretty slow. The current 500ms is way too fast for something rarely checked. Maybe once a second. There's also the possibility of creating a MouseGesture using ChatFrame1 as, and configure it so when you simply click on ChatFrame1 then StarTipTooltipMain hides. hmm