Simple Interrupt Announce

Introduction

Simple Interrupt Announce (SIA) is a World of Warcraft addon that aims to be
a relatively simple and efficient, yet flexible interrupt announcer. The main
use of such an addon is to help coordinate interrupts in raids.

Settings

SIA stores settings for how to announce interrupts based on your grouping
status. So you can have separate settings for when you are solo, in an
instance group, party, or raid.

For each of these four statuses, SIA can announce your own interrupts, and
those of other people/pets in your party/raid.

Announcing is based on modes, which decide what channel the announcement goes
to. They can be: off, self, say, instance, party, and raid.

The default settings are:

status       own    other
-------------------------
solo        self      N/A
instance    self     self
party       self     self
raid         say     self

So, when you are playing solo, you will get your own interrupts announced to
yourself, and not see others. When in an instance group or party, your own
interrupts and other peoples interrupts will be announced to yourself. When
in a raid, your own interrupts will be announced in say, and you will see
other peoples interrupts announced to yourself.

Own covers interrupts made by you or your pet, other covers interrupts made
by any player or pet in your party/raid.

Instance groups are groups/raids created by the instance finder (LFD/LFR/etc.)

Slash Commands

You can enable and disable announcing with

/sia on
/sia off

You can use

/sia <status>

to see what the modes are for that status. And

/sia <status> [own [other]]

to set the mode for own and other interrupts respectively.

Here are a few examples:

/sia party         - print current party modes
/sia solo self     - when solo, own interrupts to yourself
/sia raid say self - when raid, own to say, others to self

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

19 comments
1
2
Next →

- Reply
- #19
BeathsCurse Mar 12, 2013 at 21:20 UTC - 0 likes
@John454ss: Go

Thank you for the patience and feedback.
- Reply
- #18
John454ss Mar 12, 2013 at 20:48 UTC - 0 likes
Beta 3 of Simple Interrupt Announce fixes the taint on startup/reload problem until accessed in the addon tab. (To be fair any addon in that tab generates taint issues once those menus are generated.) I agree that almost any interaction to UIDropDownMenu causes these issues.

Your methods and approach to this problem are appreciated. Thank you for fixing something that already worked and affected only a small portion of the user base.

Last edited Mar 12, 2013 by John454ss
- Reply
- #17
BeathsCurse Mar 10, 2013 at 20:27 UTC - 0 likes
@John454ss: Go

Ok, in beta 3 I've moved the configuration panel code to a separate folder which is load on demand.

The dropdown code still taints, but at least now it is only loaded if you open the configuration panel, and you can disable it by simply disabling SimpleInterruptAnnounce_Config instead of editing lua files.
- Reply
- #16
BeathsCurse Mar 10, 2013 at 16:33 UTC - 0 likes
@CanRanBan: Go

Sounds like a good idea. I have made an attempt to add this, and uploaded another beta (should show up shortly).
- Reply
- #15
CanRanBan Mar 10, 2013 at 11:59 UTC - 0 likes
Hi there,

i have one feature request. Is it possible to get an option to show the target marker of an interrupted target? I really like your addon but miss the raid marks. I used to have them with other addons of this type but they lacked the announce of all interrupts in a group / raid. :(

Thanks in advance.
- Reply
- #14
BeathsCurse Mar 08, 2013 at 21:59 UTC - 0 likes
@John454ss: Go

It's quite maddening really. I tried disabling one addon at a time, checking the taint log to see if UIDROPDOWNMENU_MENU_LEVEL got tainted, and I ended up having disabled all addons that had an entry in the configuration options panel. I guess it is more or less impossible to use UIDropDownMenu without getting this problem, and whatever addon happens to get flagged first is the one that is blamed.

I have uploaded a beta where the dropdowns are not initialized before the configuration panel is shown. Of course this does not fix the issue, it just postpones it.
- Reply
- #13
John454ss Mar 08, 2013 at 17:23 UTC - 0 likes
This taint error spreads to the compact raid frames so a person can't use the compact raid frames with other addons/sometimes can't even click to target using the standard frames.  There are hundreds more lines (different issues) in the taint log.  They can be viewed in the taint log if you turn on "/console taintLog 2" and do a "/reload".  These errors are from running 1.0.21 with the 5.2 WoW client and no other addons.  Cleaning the WTF/cache/addon folders makes no difference.  I hope this helps to track down the issue because I like how this addon works.  I just wish I didn't have to keep taking out the GUI configuration.

3/8 11:09:30.787  Global variable UIDROPDOWNMENU_MENU_LEVEL tainted by SimpleInterruptAnnounce - Interface\FrameXML\UIDropDownMenu.lua:38
3/8 11:09:30.787   securecall()
3/8 11:09:30.787   Interface\FrameXML\UIDropDownMenu.lua:64 UIDropDownMenu_Initialize()
3/8 11:09:30.787   Interface\AddOns\SimpleInterruptAnnounce\ConfigurationPanel.lua:184 SimpleInterruptAnnouncePanel:CreateDropDown()
3/8 11:09:30.787   Interface\AddOns\SimpleInterruptAnnounce\ConfigurationPanel.lua:221 a()
3/8 11:09:30.787   Interface\AddOns\SimpleInterruptAnnounce\ConfigurationPanel.lua:199

3/8 11:09:30.953  Execution tainted by SimpleInterruptAnnounce while reading UIDROPDOWNMENU_MENU_LEVEL - Interface\FrameXML\UIDropDownMenu.lua:48
3/8 11:09:30.953   securecall()
3/8 11:09:30.953   Interface\FrameXML\UIDropDownMenu.lua:64 UIDropDownMenu_Initialize()
3/8 11:09:30.953   Interface\AddOns\Blizzard_CUFProfiles\Blizzard_CompactUnitFrameProfiles.lua:455 CompactUnitFrameProfilesGeneralOptionsFrameSortByDropdown:updateFunc()
3/8 11:09:30.953   Interface\AddOns\Blizzard_CUFProfiles\Blizzard_CompactUnitFrameProfiles.lua:184 CompactUnitFrameProfiles_UpdateCurrentPanel()
3/8 11:09:30.953   Interface\AddOns\Blizzard_CUFProfiles\Blizzard_CompactUnitFrameProfiles.lua:171 CompactUnitFrameProfiles_ActivateRaidProfile()
3/8 11:09:30.953   Interface\AddOns\Blizzard_CUFProfiles\Blizzard_CompactUnitFrameProfiles.lua:45 CompactUnitFrameProfiles_ValidateProfilesLoaded()
3/8 11:09:30.953   Interface\AddOns\Blizzard_CUFProfiles\Blizzard_CompactUnitFrameProfiles.lua:25
- Reply
- #12
BeathsCurse Feb 28, 2013 at 07:24 UTC - 0 likes
@John454ss: Go

Thanks for the report. Yes, I noticed the tainting issue as well while working on the configuration panel code, and it has gotten worse since I started creating the menus later in the loading process to avoid some issues with the saved configuration.

Like you say, it appears to be a general problem with using the UIDropDownMenu control, and I might end up having to write my own.

I actually made an effort to make the configuration panel code entirely separate from the other code, so it was possible to just disable loading of that one file, and have the original functionality. I am happy somebody found that little 'feature' :-).
- Reply
- #11
John454ss Feb 27, 2013 at 11:05 UTC - 0 likes
This program is suffering from the very common issue of compact raid frame LUA errors. Most forums say it's probably caused by UIDropDownMenu interaction.

This is how to recreate the issue. Clear the WTF folder. Turn off all addons excepts SIA. (Using version 1.0.20.) Use the standard raid frames. Go into the GUI for the program and select some stuff on/off. Next go into any battleground or LFR and when in combat and someone enters/leaves LUA errors start popping up. You can also go into battlegrounds and open the map to report someone AFK and Blizzard pops up a warning saying the addon has been blocked and is trying to use a protected function.

Update: Actually looking at your files I removed the ConfigurationPanel.lua and went strictly command line. No tainting issues at all. Command line only, but everything works again. The culprit lies in that file and I see UIDropDownMenu in there. I can't offer solutions. I"m just pointing out problems. Sorry. I love this program and how it works.

Last edited Feb 27, 2013 by John454ss: Typo and new findings
- Reply
- #10
DeHejner Feb 03, 2013 at 20:45 UTC - 0 likes
Couldnt find any problems so far :)