Alright I will look into it on there forums more. I just find it strange it only happens when I hand control over to prat. Any small error I receive also seems to say it was the FrameXML code that failed not so much Prat.
I'm still experience a chat tabs issue, as soon as I allow Prat to take over my frames' tabs, I will receive a WoW 132 error when I attempt to move them. The error will not occur however if I move the default or combat log chat frames. I've also seen posts of these on the WoW forums and still have no solution other than to not allow prat to have control over those frame. Tested with Prat as the only addon running.
Okay... It appears to be any frame BUT the original and the combat log and I don't quite understand why it causes a WoW 132 Error. Can be reproduced on all my toons with only Prat running.
EDIT: When running all my addons I get this same error on occasion. I don't play long enough without my addons to really reproduce this specific error but since it has to do with chat tabs it seems like a good bet this is the issue.
I fixed my color issue awhile back, another mod decided that it wanted to control the chat despite me telling it no and then when i disabled all my addons I kind of removed the coloring anyway >.>
I've run into another strange issue though. I recently was using DamnChatTabs (which I removed) but found that Prat has the same features and thus I allowed Prat to take control of my Chat Tabs. Was all good but whenever I drag ANY chat frame I get a WoW 132 error (crash). If I click to change tabs it all works fine. Also "Prevent Dragging" does not prevent this error; if it's on it still occurs. All addons disabled nothing left going but all 3 Prat addons. I don't think taking a screenshot really helps in this case but I can if you want.