Gyth posted a chat linking fix for EavesDrop, i tryed and made it possible with Cascade too.
go to World of Warcraft\Interface\AddOns\Cascade\CascadeCore.lua
Replace "ChatFrameEditBox" with "ChatFrame1EditBox" in every string (should be 2) in the file
Enjoy
Thx again to Gyth for posting it

Chat linking doesnt work anymore in 3.3.5

Ileft comments on wowace, going to try here. The load time for this addon just keeps increasing weekly. First it was a 6 second load, then 12, and now 23 second load time for just this one addon. I'm using !warmup to track this.

Any ideas why this is happening or is there some known conflict with another addon?

3.3.5 Error when trying to link the events to chat:

Like EavesDrop, is there a way to change the alpha of the Player and target text on the top of the frame? :O I'd like to fade it out any way possible Or, you can direct me maybe where I can change the alpha of it in the Lua possibly? Thanks in advance

Is there a way to tweak the code to add click-through to the frame ?
I use Cascade on the middle right of my screen and it bugs me when I try to turn the camera and end up right clicking Cascade !

I dream of an option that would allow me to click-through when in fight, and clic Cascade to see the informations when not.

Keep up the good work.

The lag when scrolling is gone now (since the tooltip no longer updates on every scroll event), and the lag when moving your mouse over the window has gotten a tiny bit better I think, but that might just be my imagination.

I do suspect that the fault doesn't lie with your addon, but with either TipTac or some ace lib (or a combination or tiptac and a lib). Since when I turn on CPU profiling and turn off addons one by one after checking which of them displays as using huge amounts of CPU time when the tooltip lag occurs, each time I disable an addon another one starts "using" CPU instead. (I assume that this is just a limitation of the profiling addon I use, that instead of displaying libraries seperatly, it just sets the first addon it encounters that uses that lib as the "owner" of it, even though many other addons may use it aswell). I'll look into it some more later on to track down the exact cause.

Getting this error on login (useing german client):

[2010/02/09 23:25:35-53-x12]: Cascade-1.0.1\CascadeCore.lua:736: invalid capture index
Cascade-1.0.1\CascadeCore.lua:736: in function `?'
CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[13]":4: in function <[string "safecall Dispatcher[13]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[13]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

---

1) Yes, it actually "stutters", FPS drops down <1.
2) No, it only happens when scrolling over actual combat log history (ie, only when the tooltip shows). It doesn't only happen during scrolling, just moving the mouse quickly up and down over the cascade window causes the lag, although to a lesser degree.
3) I'll have to get back to you about this tomorrow, I can't log on at the moment.
4) Yes.

Here's a list of my addon folder (not all of these addons are enabled though): http://pastebin.ca/1788648

I get this aswell, for me it's caused my the addon "Altoholic" (which hooks the tooltip function). It starts using up massive ammounts of CPU time. (Altoholic that is, not Cascade)

Edit: After disabling Altoholic it turns out that TipTac starts using all the CPU time instead. Guess Altoholic only showed up as the cause in my CPU profiling addon because it hooked the tiptac function.

I was curious as to why this was updated? I see no change log so I'm not sure as to why I need to update to this new version vs. the other version? Sorry to be a bother :O