HeadCount

85 - Error when using WIM

What steps will reproduce the problem?
1. Download latest version of WIM and enable it.
2. Start a new raid and announce wait list
3. Incoming whisper from a guildie will trigger error

What is the expected output? What do you see instead?
The expected output would be to add people to the wait list when they whisper the command "wl add". It seems to be doing this just fine, except it also triggers an error.

What version of the product are you using?
1.5.6

Do you have an error log of what happened?
Error occured in: Global
Count: 1
Message: ..\AddOns\HeadCount\RaidTracker.lua line 1319:
   Unable to determine if incoming message is supported because the message is nil.
Debug:
   [C]: ?
   [C]: assert()
   HeadCount\RaidTracker.lua:1319 IsSupportedIncomingMessage()
   HeadCount\HeadCount.lua:216 filterFunc()
   WIM\WIM.lua:293 honorChatFrameEventFilter()
   WIM\Modules\WhisperEngine.lua:276 handler()
   ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:252 popEvents()
   ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:146 Release()
   WIM\Modules\Filters.lua:243 CHAT_MSG_WHISPER_CONTROLLER()
   WIM\Modules\Filters.lua:148
      WIM\Modules\Filters.lua:118
   WIM\Modules\Filters.lua:188 callback()
   WIM\Libs\LibWho-2.0\LibWho-2.0.lua:483 RaiseCallback()
   WIM\Libs\LibWho-2.0\LibWho-2.0.lua:407 ReturnWho()
   WIM\Libs\LibWho-2.0\LibWho-2.0.lua:742 ?()
   WIM\Libs\LibWho-2.0\LibWho-2.0.lua:753
      WIM\Libs\LibWho-2.0\LibWho-2.0.lua:752

Please provide any additional information below.
I started out by posting this at the WIM community but according to Pazza (the WIM developer) the error is likely to be tied to HeadCount and not WIM.

User When Change
Blazeflack Sun, 26 Apr 2009 19:19:28 Changed status from New to Invalid
Blazeflack Fri, 17 Apr 2009 09:06:57 Changed description:
     [C]: assert()
     HeadCount\RaidTracker.lua:1319: IsSupportedIncomingMessage()
     HeadCount\HeadCount.lua:216: filterFunc()
-    WIM\WIM.lua:306: honorChatFrameEventFilter()
+    WIM\WIM.lua:293: honorChatFrameEventFilter()
     WIM\Modules\WhisperEngine.lua:276: handler()
     ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:252: popEvents()
     ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:146: Release()
Blazeflack Thu, 02 Apr 2009 15:54:42 Changed description:
     [C]: assert()
     HeadCount\RaidTracker.lua:1319: IsSupportedIncomingMessage()
     HeadCount\HeadCount.lua:216: filterFunc()
-    WIM\WIM.lua:304: honorChatFrameEventFilter()
+    WIM\WIM.lua:306: honorChatFrameEventFilter()
     WIM\Modules\WhisperEngine.lua:276: handler()
     ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:252: popEvents()
     ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:146: Release()
----------------------------------------
     WIM\Libs\LibWho-2.0\LibWho-2.0.lua:753:
        WIM\Libs\LibWho-2.0\LibWho-2.0.lua:752

+
  Please provide any additional information below.
  I started out by posting this at the WIM community but according to Pazza (the WIM developer) the error is likely to be tied to HeadCount and not WIM.
Blazeflack Fri, 27 Mar 2009 13:41:03 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 4 comments
  • Avatar of Blazeflack Blazeflack Sun, 26 Apr 2009 19:19:48

    New version corrected this behavior. Ticket closed.

  • Avatar of Blazeflack Blazeflack Fri, 17 Apr 2009 09:06:57

    Changed description to match the error given with latest release of WIM.

  • Avatar of Blazeflack Blazeflack Fri, 03 Apr 2009 13:38:12

    The error blocks the incoming whisper from ever being shown. This means that if I use HeadCount and WIM together, the first whisper I receive while being in a raid will never go through but instead trigger an error. After that it seems to work fine.

  • Avatar of Blazeflack Blazeflack Sun, 29 Mar 2009 21:55:34

    Just realized all incoming whispers will trigger this error if I have WIM enabled along with HeadCount and not just the whispers containing the "wl add" command.

  • 4 comments

Facts

Last updated on
26 Apr 2009
Reported on
27 Mar 2009
Status
Invalid - This was not a valid report.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.

Reported by

Possible assignees