FlareUP : Raid Mods : World of Warcraft AddOns

(4 Kb)

Download

Updated: 02-21-12 08:40 AM

Add Favorite

Install Help

Pictures

File Info

Tested:	Hour of Twilight 4.3
Updated:	02-21-12 08:40 AM
Created:	11-01-10 08:51 PM
Downloads:	2,388
Favorites:	30
MD5:

FlareUP

Version: 1.36-40300

by: Dridzt [More]

FlareUP
... is yet another addon for using the new World Markers (flares)
as a party leader, raid leader or officer without going through the compact raid manager.

So why another one?

It's a different implementation that doesn't rely on the usual
Code:
```
/click CompactRaidFrameManagerDisplayFrameLeaderOptionsRaidWorldMarkerButton
/click DropDownList1Button1
```
macros every other world marker addon is using.
I prefer the small button approach that I can drag to any side of the screen to a bar.
It has marker timers.
*new* v1.33 and onwards adds world marker key-binds to the Game Options.

Alright... are you going to add?
-button customization
-sharedmedia support,
-sounds and libsink announce for expiring markers,
-bars instead of text timers,
-dancing hippos
-...

Probably not, it suits me fine as it is.

Hope you find it useful as well.

Configuration:
/flareup pos
Show the button out of party for positioning. Flares will not work. Type it again to hide.
/flareup timers
Toggles timers on/off.

Known issues:
- Timers do not persist following a reload.
- I've tried to make the timers smart but there is a small chance of "false" positives
depending what you do after you load a flare to the cursor and before you actually put it down.
(fx clicking an actionbutton instead of the "world" or clicking out of range)

v1.36-40300
------------
- remove some debug code from secure keybinds (no functional changes)

v1.35-40300
------------
- more improvements to marker timers
(mouse buttons 3 to 5 could confuse the addon, and /cwm 0 wasn't clearing timers properly)
- attempt to fix the 'C stack overflow' error reported by Zidomo @wowi.
(can't reproduce it myself but I have an idea what might have been the issue)

v1.34-40300
------------
- bufix 4.3 enable/disable logic (was incorrectly enabling in raid when not RL/assistant)
- world marker timer changes
-- timer shadow and anchoring.
-- timers count down again. Assumed time-out of 1hour (unverified!)
- keybind menu changes (Esc -> Keybinds -> FlareUP)

v1.33-40300
------------
- update for raid manager frame changes
- new feature: world marker key-binds
- .toc update, compatible with Hour of Twilight (4.3)

v1.32-40200
------------
- .toc update

v1.32-40000
------------
- don't leave timers and updates running in the background when leaving a party / losing lead.

v1.31-40000
------------
- seems world markers are persistent after 4.0.6 (last until recalled) and not 5mins.
Timers will count up instead of countdown.

v1.3-40000
-----------
- WoW 4.0.6 API update.
FlareUP timers now respond to individual flare clears as well as "clear all".

v1.2-40000 (unreleased)
-----------
- another try at preventing taint

v1.1-40000
-----------
- More aggressive detection of combat status following a reloadUI or logging in combat.

Archived Files (9)

File Name	Version	Size	Author	Date
FlareUP	1.35-40300	5kB	Dridzt	12-07-11 07:33 PM
FlareUP	1.34-40300	5kB	Dridzt	12-04-11 05:33 AM
FlareUP	1.33-40300	5kB	Dridzt	11-28-11 03:47 AM
FlareUP	1.32-40200	3kB	Dridzt	07-01-11 05:26 AM
FlareUP	1.32-40000	3kB	Dridzt	02-17-11 05:58 AM
FlareUP	1.31-40000	3kB	Dridzt	02-14-11 05:59 PM
FlareUP	1.3-40000	3kB	Dridzt	02-09-11 09:27 AM
FlareUP	1.1-40000	3kB	Dridzt	11-23-10 09:42 AM
FlareUP	1.0-40000	3kB	Dridzt	11-01-10 08:51 PM

Comment Options

12-07-11, 07:40 PM
Dridzt A Molten Giant Forum posts: 668 File comments: 667 Uploads: 66	@Zidomo, Error should be fixed in v1.35-40300, re-enable timers and see if it's gone. Last edited by Dridzt : 12-12-11 at 07:36 AM.

12-04-11, 02:33 AM

Dridzt

A Molten Giant

Forum posts: 668

File comments: 667

Uploads: 66

Originally Posted by Zidomo

Code:

["message"] = "C stack overflow:\n<in C code>: ?
            ["type"] = "error",
            ["locals"] = "(*temporary) = WorldFrame {\n 0 = <userdata>\n}\n(*temporary) = \"RightButton\"\n(*temporary) = <function> defined =[C]:-1\n(*temporary) = WorldFrame {\n 0 = <userdata>\n}\n(*temporary) = \"RightButton\"\n = <function> defined =[C]:-1\n = <function> defined @Interface\\AddOns\\FlareUp\\core.lua:100\n",
            ["session"] = 4994,
            ["counter"] = 536,
        }, -- [1000]

Disable timers temporarily.

12-03-11, 10:55 PM
Zidomo A Cliff Giant Forum posts: 76 File comments: 1057 Uploads: 0	Gave this a go in the new patch; the mod got so excited...it overflowed. v1.33-40300, WoW 4.3 live, US English client/server. Hadn't used in a while, turned on on an 85 character before joining a guild raid; the only character have used this on before. Character SV was carried over from an old version. SV at the end of the raid after logging out: Code: FlareUPPC = { ["showTimers"] = true, } Was not a lead or assist in this raid, so couldn't set flares. Adjusted the position of the FlareUP frame from its default a couple times in the raid (out of combat). Might have clicked the button accidentally. 2 hours into the raid (no relogging or crashing), the following error occurred at some point. It repeated many (many) times in the next 1/2 hour before could get a minute to disable the mod and relog. After first noticing the error (at about the 74-counter mark), made sure not to click the frame button. The counter still went up during combat, however: Code: ["message"] = "C stack overflow:\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n...:\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n<in C code>: ?\n", ["type"] = "error", ["locals"] = "(temporary) = WorldFrame {\n 0 = <userdata>\n}\n(temporary) = \"RightButton\"\n(temporary) = <function> defined =[C]:-1\n(temporary) = WorldFrame {\n 0 = <userdata>\n}\n(temporary) = \"RightButton\"\n = <function> defined =[C]:-1\n = <function> defined @Interface\\AddOns\\FlareUp\\core.lua:100\n", ["session"] = 4994, ["counter"] = 536, }, -- [1000] Last edited by Zidomo : 12-03-11 at 10:58 PM.*

04-29-11, 08:51 AM
apurelinquished A Kobold Labourer Forum posts: 0 File comments: 1 Uploads: 0	So far this addon is absurdly beautiful. sniff This is the only flare marker addon that hasn't vomited a bunch of "<addon> has been blocked due to performing an action available only to the Blizzard UI" on my screen. THANK YOU!

04-22-11, 11:27 AM
jmcgrath A Kobold Labourer Forum posts: 0 File comments: 176 Uploads: 0	Hi, I also get the blocked by Power Auras etc... But my question is: Since install, The button is there, and commands are working... but there is no flag in my button, so no way to access the drop down menu. inside party ofc Please advise. Thanks. __________________ Last edited by jmcgrath : 04-22-11 at 11:29 AM.

02-14-11, 10:29 PM
Kendian A Firelord Forum posts: 467 File comments: 115 Uploads: 6	Oh, hey, something small, unobtrusive, and fully funstional. I dig it. GOOD job! __________________

12-29-10, 06:39 AM
Dridzt A Molten Giant Forum posts: 668 File comments: 667 Uploads: 66	As a slight update to this. I've run without FlareUP or ANY marking addon with flare functionality for 2 weeks. I still get action blocked errors when trying to use the default raid manager dropdown, blaming Ace3, Recount, or any number of seemingly random addons. I'd say the flares dropdown is just extremely easy to taint, similar to the unitpopup menu and is something on Blizzard's end to make harder to taint. (or unprotect already.. I don't see what in world markers needs to be protected)

12-16-10, 04:45 PM
Dridzt A Molten Giant Forum posts: 668 File comments: 667 Uploads: 66	Yes something changed in the latest mini-patch. I get the same from either Mapster or Recount (basically anything with long dropdowns if I've opened said dropdowns at least once in combat). There is not a whole lot to debug in my addon, the base idea is very simple. Instead of using macros it re-anchors and moves the actual raid manager dropdown. It doesn't try to hide or show it and does nothing to trip taint. (theoretically) It additionally does the anchoring and moving out of combat only. Even if there was something I could think of to "fix" I wouldn't do it now, busy with the game. So my advice is "use something else". I will either take it down or mark it as broken for now. I expect to come back to it at a later time to see if it's salvageable. Edit: To clarify this is not an issue with FlareUP per se. It's the same crap that's been happening with Blizzard's Dropdown system and for example Set Focus for years. But the end-result is the same for the user so I won't say "I wash my hands", just use another addon that doesn't rely on a dropdown menu to set flares. Last edited by Dridzt : 12-16-10 at 04:48 PM.

12-16-10, 02:40 PM

Zidomo

A Cliff Giant

Forum posts: 76

File comments: 1057

Uploads: 0

Well, clicking a (color) World Marker line initiates taint and refuses to place a flare.

FlareUP v1.1-40000, WoW 4.0.3.13329 live. Click a line as above from the FlareUP tooltip and get an infamous Blizzard taint "Disable/Ignore" popup box...naming Mapster (1.4.0-7-g410b3cf). None of the (color) World Marker lines work; they all initiate the BLizzard taint warningbox.

In taint.log:

Code:

12/16 07:55:54.515  An action was blocked because of taint from Mapster - 
12/16 07:55:54.515      PlaceRaidMarker()
12/16 07:55:54.515      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameManager.lua:103 func()
12/16 07:55:54.515      Interface\FrameXML\UIDropDownMenu.lua:636 UIDropDownMenuButton_OnClick()
12/16 07:55:54.515      DropDownList1Button1:OnClick()
12/16 07:55:59.046  An action was blocked because of taint from Mapster - 
12/16 07:55:59.046      PlaceRaidMarker()
12/16 07:55:59.046      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameManager.lua:103 func()
12/16 07:55:59.046      Interface\FrameXML\UIDropDownMenu.lua:636 UIDropDownMenuButton_OnClick()
12/16 07:55:59.046      DropDownList1Button3:OnClick()
12/16 07:56:02.703  An action was blocked because of taint from Mapster - 
12/16 07:56:02.703      PlaceRaidMarker()
12/16 07:56:02.703      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameManager.lua:103 func()
12/16 07:56:02.703      Interface\FrameXML\UIDropDownMenu.lua:636 UIDropDownMenuButton_OnClick()
12/16 07:56:02.703      DropDownList1Button5:OnClick()

As a comparison, using instead TargetCharm's world marker addition (on a different character in combination with Mapster) works without issue.

11-28-10, 01:44 PM

Dridzt

A Molten Giant

Forum posts: 668

File comments: 667

Uploads: 66

Originally posted by Invertigo
I don't suppose your mod allows keybinding of flares?

No sorry, it's not that I don't want to support it but PlaceRaidMarker is protected and macros using /click eventually taint.

You can get a separate addon for it.
At least if it taints you won't blame me for breaking your game

Example: Raid Flare Key Binding

11-28-10, 11:33 AM
Invertigo A Defias Bandit Forum posts: 2 File comments: 46 Uploads: 0	I don't suppose your mod allows keybinding of flares? __________________ Once you go gnome, you never go home...

11-11-10, 11:36 AM

Dridzt

A Molten Giant

Forum posts: 668

File comments: 667

Uploads: 66

Originally posted by LiNK2088
When I press one of the marks, I get a popup saying: PowerAuras has been blocked from an action only available to the Blizzard UI.

And yes I have Power Auras Classic installed.

I am using both this and Power Auras and haven't had any issues.

That does not mean it's not a likely cause of the issue although I've taken all precautions I could to prevent it.

1. Is the problem easily reproducible with some set of actions or does it happen "sometimes"?

2. If the answer to #1 is "I can make it happen anytime I want" then please disable FlareUP before logging on and try setting flares from the default compact raid manager.

I have a feeling you'll have same problem and another addon is the cause.

If you don't want to go to the trouble of doing such tests then only do this:
/console taintLog 1
while playing and make the error happen again.

Check your \World of Warcraft\Logs\taint.log for the first addon mentioned for that specific date/time.

11-11-10, 11:27 AM
LiNK2088 A Murloc Raider Forum posts: 6 File comments: 91 Uploads: 0	When I press one of the marks, I get a popup saying: PowerAuras has been blocked from an action only available to the Blizzard UI. When disabling Power Auras Classic: Buttons, it does work. Last edited by LiNK2088 : 11-11-10 at 11:32 AM.

Report this File

Category Jump: