Explaination on WIM and it's Event Handling

[DevTeam] [lothaer]: Posted a new download in the skins forum check it out
[DevTeam] [lothaer]: Zeke, Maziel, Pazza, Nachonut, sylvanaar, Kaidenn, Astaldo where are you?
[DevTeam] [lothaer]: It would be a real shame if WIM was left to die.
[DevTeam] [lothaer]: i think these forums are dead, Sylvanaar dosnt post on them as he only bug fixes when possible. WIMs future isnt very bright
[Guest] [justgiz]: Yea, its rather sad.
[Guest] [silvercola]: I wish it had skype
[DevTeam] [lothaer]: noy possible for a addon to do.
[DevTeam] [lothaer]: ...........
[Guest] [elzershark]: where is the download file?
lothaer beckons everyone over to you.
[DevTeam] [lothaer]: has anyone been able to take WIM to the beta yet?
[DevTeam] [lothaer]: PTR*
[DevTeam] [Maziel]: *sticks head up and looks around*
lothaer cries.
[DevTeam] [lothaer]: who the hell flagged my post as spam?
[Guest] [primalforce]: Hey guys
[DevTeam] [lothaer]: hello Primalforce.
[DevTeam] [lothaer]: PAZZA COME BACK!!!
[DevTeam] [Nachonut]: Ahhh memories
[Guest] [Ignis]: wtb update
[DevTeam] [lothaer]: soooo.....
Pazza starts to complain... Kinda reminds you of Sloans dont it?
[Guest] [Hentaya]: No more wiki?
[Guest] [Hentaya]: All the wiki links seem to bring me to the forums.
[Guest] [menace97]: the latest wim (3.5.9) i download still reads in-game as 3.4.2. ?
[Guest] [Hentaya]: Good thing the shoutbox doesn't have timestamps.
[Guest] [ravensong]: Is WIM going to be updated for the new patch? It gets a LUA error every time people log on bnet or pst me, because "
[Guest] [ravensong]: "surname" is now a nil value.
[Guest] [Dethedrus]: Since WiM is obviously quite dead, is there ANYTHING else out there that even comes close to replicating it's functionality?
[Guest] [Harshmage]: So the "surname" can be removed from the realID detection, in WIM.lua
[Guest] [Harshmage]: but fixing the tutorial popup and other errors is probably not going to happen without a major rework
[Guest] [menace97]: quite dead?
[Guest] [Nytetears]: I am trying out tell track I wish WIM would update I much prefer it but there are too many errors to try and use it now
[Guest] [Erudan]: Wim is being updated on Curse.
[Guest] [Chiaki]: Hello guys! I'm the one who did the German translation of WIM. The translation is somewhat old so tell me where to provide a new version .
[DevTeam] [lothaer]: Check out my new post in the General Discussion. Please report any errors as I can't check them myself.
lothaer pokes Pazza. Hey!
lothaer is overcome with boredom. Oh the drudgery!
lothaer roars with bestial vigor. So fierce!
lothaer cries.
lothaer falls asleep. Zzzzzzz.
lothaer , in quiet contemplation, mourns the loss of the dead.
lothaer tells a joke.
lothaer yawns sleepily.
[DevTeam] [lothaer]: Sylvanaar
[DevTeam] [lothaer]: 22/10/12
[DevTeam] [lothaer]: updated the download
[DevTeam] [lothaer]: check out my new post in the Skin thread
[DevTeam] [lothaer]: 11/11/12
[DevTeam] [lothaer]: 23/2/13

[Pazza]

WIM reacts to 2 event sources. The first is from the ChatMessageFrame and the other is from its own internal events. The reason behind this is, the default chat frame registers events based off of chat tabs. Example: Chat, Combat, Userdefined... If whispers are shown on more than one tab, each time a whisper is sent or received, each tab triggers the event. This causes duplicate messages to be caught by WIM. On the flip side, if whispers are hidden (therefore unregistered) on all tabs, WIM will no longer receive whispers when depending solely on the chat frame itself. That being said, the ChatFrame is not a dependable source of whispers.

The reason WIM still listens to events even though they aren't dependable. Simply so that it can supress the messages themselves from the chat frame.

If you want your addon to hook into WIM, do NOT hook its message handler. Instead you would want to hook the function that creates and registers the actual conversation windows. Further documentation on how to do so can be found under the WIM API section that I created on this website.

http://www.wimaddon.com/wiki/WIM:API

If you have any questions, please feel free to ask them in this thread.

[canidae]

this explanation is fair and i see why this is done like this, but i still disagree with the solution.
while you may claim that the chatframe is not a dependable source of whispers, i'd say that's the most dependable source of them all, since this is where the user actually set which messages should be shown and which shouldn't. if the user uncheck whispers from all the chatframes i'd say that's a pretty good sign that the user don't want any whispers at all.
duplicate messages can be countered to prevent them from showing up twice or more.
but it's quite obvious that we disagree here and won't get anywhere, so i'll just see about creating another addon that hack in support for wim in stfu.

[Pazza]

This event handling is new to WIM 2.0 and was the final change I made that seems to have corrected everyone's issues with receiving whispers. For that reason alone, I want to keep it until there is something better.

If you want an example on how to get your addon to work with WIM, it is to my knowledge that SpamSentry has made itself compatible with WIM. The author has confirmed this with me. You should check it out.