Markk

Seems to have fixed itself now.

How does one submit a ticket for this properly? I clicked the support button, selected 'Character' (seemed closest to me), typed in the issue, and submitted. Chat said 'Game Masters do not handle bug reports.' Did it go through or not? Did my question go through some filter for keywords and it was determined that my question is a bug report, or are all character-related questions bug reports. If the latter, why does the option to send a question for it exist in the first place?

Having the exact same issue. In the same game session, I was whispering someone and all of a sudden noticed I'm not seeing my own messages any more. Did the same thing: disabled addons and deleted WTF folder. Still can't talk in whisper or /say, yet I can talk in guild.

Just made a mock-up addon to show how I have it set up (I've tested this code too and the problem persists) This file loads first based on ordering in .toc: This one loads after the above: I have an XML too, but it doesn't do anything except create a dummy frame to call the event functions. Here is the output of the chat messages: The second call doesn't pass "TestArg" to the original function, but it does pass it to the post hook. What's going on here? This is not how I expect it to behave.

@Ike so if I changed all functions to SomeTable.SomeFunction = function(arg) , without the self in the parameters, it would work too? It's just the function shorthand that adds the self parameter?

I also added the RegisterEvents in KTM_Frame.xml lines 1019-1021 and the functions in KTM_Core.lua at lines 179-207 (the last function at lines 209-215, KTM_OnEvent, doesn't do anything and can safely be removed if you wish).

Try this. I haven't fully tested it, but it does hide it when I log in. However, I've not been in a party the while I've been testing, so perhaps it's hiding because it always will and the checks are broken. But give it a try and let me know. Currently, there is no option to disable it (might add commands later if I'm bored). If you want to show it temporarily, you can do /klhtm g s to show it until your party or raid roster is updated (i.e. someone enters or leaves). If you want to disable it, you'd have to remove the code between lines 1033-1037, inclusive, in KTM_Frame.xml and relog (or just reinstall an unmodified version.)

Turns whispers off completely.

I'm new to programming for WoW. I'm trying to backport a small addon, but I'm having issues with self being nil. Here is the complete code (excluding the XML). As one can see, I have commented out some functions that call on self such as on lines 24 and 32. This is because I was getting self being nil errors. But now it seems to have gotten to the point that I can't avoid these errors. Now line 6 also gives nil errors for self. This is when updateFS is being called from OnEnter and OnLeave, but it might be safe to assume this is an issue regardless of which event calls it. It am new to Lua and WoW programming, but it is my understanding that when doing something like tab:SetScript("OnEnter", OnEnter) the event (first arg of SetScript) will pass its args to the function that will be called (second arg of SetScript). According to this, OnEnter has self (reference to the frame for which the event was called) as the first arg. Everything I've read leads me to believe that. However, nothing I've read about this has been for 1.12, so I think that therein lies the issue if it isn't human error. My other hunch is that I may have to do everything event related through XML because I was having issues getting OnLoad to work doing it all through Lua (though the issue here is that self is nil, not that functions aren't being called for events). I haven't browsed through many addons yet to see how this is dealt with elsewhere. However, one that I saw which deals with events on frames used XML for all events and was using this (same as self) in the event functions. I'll try that tomorrow but I figured I might as well ask here too; I might get a response over night. So, do events not pass self in 1.12, or am I doing something wrong? If it's the former, how can I accomplish the same thing in 1.12?

Thanks to both of you. I just had to use this as the first argument for the event handlers' calls to the updateFS function. Was this changed in later versions of WoW so that it works similar to how I originally described it? Unrelated question: is there an alternative to hooksecurefunc in 1.12? I'm guessing the reason errors are thrown is because it doesn't exist in 1.12. Should I just try a normal post-hook and hope it works?