Omen3 comes with LDB *and* FuBarplugin support. So if you use something like FuBar and LDBtoFubar, you'll end up in trouble because you end up with 2 copies of Fubar plugin named the same and interfering.
"LDBtoFubar" (which actually is Broker2FuBar) append a suffix to the plugin name, e.g. so it would be named something like "Omen3_B2F". Both shouldn't conflict with each other. At most they are redundant. You can prevent Broker2FuBar to create a FuBarPlugin from Omen3 DataObject.
Omen3 comes with LDB *and* FuBarplugin support. So if you use something like FuBar and LDBtoFubar, you'll end up in trouble because you end up with 2 copies of Fubar plugin named the same and interfering.
Same for using a LDB display type addon, and using FuBartoLDB.
Hmm.. I _need_ Fubar2Broker in order to use some Fubar-addons I use. Why not do like BigWigs and oRA2, Just ditch the Fubar support? ;)
Hmm.. I _need_ Fubar2Broker in order to use some Fubar-addons I use. Why not do like BigWigs and oRA2, Just ditch the Fubar support? ;)
And ClosetGnome? :p
Personally, even though I'm 90% LDB already, keep the FuBar support. Let the user choose - that's the spirit of Ace, freedom to choose which other/supporting addon you want to use/partner with it. ^_^
But then again, with Broker2Fubar in existence, why keep the support? Lol, so conflicting. (I was actually surprised seeing my FuBar addons suddenly appearing in LDB :p like those you mentioned.)
Well, as I am currently finding out, Broker2Fubar doesnt work as well as it could/should.
I cant access the options for any of the LDB only addons on FuBar using B2F.
So I am having to use StatBlockCore to display those addons, and messing around with various options and using manual positioning to get them where I want them.
All this would be so much easier if these addons kept the Fubar support they used to have.
From what I saw of the alpha, it looks like it can definitely be ready by Tuesday. My only issue is the bug I had, and the default size of the title (which can be changed manually by players). Other then that, it looks good to go.
I've made some changes to fix the FuBar minimap button issue.
Both LDB and FuBar are still supported. I've made a further change so that during PLAYER_LOGIN:
if LibStub("LibDataBroker-1.1", true) and not IsAddOnLoaded("Broker2FuBar") then
-- create Broker launcher
end
if LibStub:GetLibrary("LibFuBarPlugin-3.0", true) and not IsAddOnLoaded("FuBar2Broker") then
-- create FuBar plugin
end
This will mean that it will create the appropriate plugin, either FuBar or Broker, but not both if FuBar2Broker or Broker2FuBar is detected. Of course, if you run both Statblocks and Fubar, then both will get created.
I've added in a line of code to save the anchoring to fix the autocollapse toggle.
I've added in audible/visible threat warning options and class filters in the latest commit.
This will mean that it will create the appropriate plugin, either FuBar or Broker, but not both if FuBar2Broker or Broker2FuBar is detected. Of course, if you run both Statblocks and Fubar, then both will get created.
Thanks for this check.
It would be nice if other authors would use this check, too.
Localization is still needed for most languages. deDE and frFR have been included. The curse version doesn't have frFR yet until I make a new beta/release tag.
Thank you for posting it to wowinterface. The previous version there hadn't been updated since May IIRC, which means it was badly outdated. I just hope that more authors do the same (publishing to WoWI) instead of taking the easier Curse-only route (though that is their choice and they can't be blamed for it).
Thanks a ton to Xinhuan and anyone else who helped get this out. You guys don't get enough credit for all the work you put in to keep us all playing and having a good time doing it.
In the FAQ in Omen3 there are instructions for making Omen3 look like Omen2 by changing the Background and Borders to the Blizzard Tooltip style, the Background to black and the border color to blue.
That's awesome.
Except I can't figure out where those options are to change them.
I don't seem to have a mini-map icon to interact with Omen3 (it might be covered, but I con't find it) so I can only get to the options through pressing ESC, choosing Interface and finding Omen under the Add Ons tab.
I really miss the transparency and some of my guild mates are threatening to drop the add if we can't get that back.
Any clues what I'm doing wrong? Thanks.
Edit: Nevermind - logged out, logged back in and suddenly had more choices. =)
I notice Omen3 appears to have the ability to track threat on a focus target. I'm not sure if this has been mentioned before, but would it at all be possible to allow dual tracking (two Omen frames) of target threat and focus threat under the new Blizzard-standard system? Alternatively, a keybind capable of toggling the primary Omen display would be a step toward this.
Currently, there is no intention to display threat on more than 1 target at a time (so choose between your target or your focus one). I'll add a keybind.
Something I had macro'ed with Omen2 was switching to AoE mode whenever I cast an AoE spell, and switching to Single-Target mode whenever I cast my primary nuke.
Really not sure if it'd be worth doing something like this in Omen3 given that there's alot less information to go around. But it certainly would be handy if Omen were able to detect these spell cast events all by itself. An Auto Mode feature would be neat, but long after the patch dust has settled, if at all. /hug!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium"LDBtoFubar" (which actually is Broker2FuBar) append a suffix to the plugin name, e.g. so it would be named something like "Omen3_B2F". Both shouldn't conflict with each other. At most they are redundant. You can prevent Broker2FuBar to create a FuBarPlugin from Omen3 DataObject.
Hmm.. I _need_ Fubar2Broker in order to use some Fubar-addons I use. Why not do like BigWigs and oRA2, Just ditch the Fubar support? ;)
And ClosetGnome? :p
Personally, even though I'm 90% LDB already, keep the FuBar support. Let the user choose - that's the spirit of Ace, freedom to choose which other/supporting addon you want to use/partner with it. ^_^
But then again, with Broker2Fubar in existence, why keep the support? Lol, so conflicting. (I was actually surprised seeing my FuBar addons suddenly appearing in LDB :p like those you mentioned.)
I cant access the options for any of the LDB only addons on FuBar using B2F.
So I am having to use StatBlockCore to display those addons, and messing around with various options and using manual positioning to get them where I want them.
All this would be so much easier if these addons kept the Fubar support they used to have.
<addon>
FuBar_<addon>
Broker_<addon>
And as necessary other such support plugins ofc, like ButtonFacade_<addon>
The big upside is that a user who wants to can delete the folders they don't use, anyways.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBoth LDB and FuBar are still supported. I've made a further change so that during PLAYER_LOGIN:
if LibStub("LibDataBroker-1.1", true) and not IsAddOnLoaded("Broker2FuBar") then -- create Broker launcher end if LibStub:GetLibrary("LibFuBarPlugin-3.0", true) and not IsAddOnLoaded("FuBar2Broker") then -- create FuBar plugin endThis will mean that it will create the appropriate plugin, either FuBar or Broker, but not both if FuBar2Broker or Broker2FuBar is detected. Of course, if you run both Statblocks and Fubar, then both will get created.I've added in a line of code to save the anchoring to fix the autocollapse toggle.
I've added in audible/visible threat warning options and class filters in the latest commit.
Thanks for this check.
It would be nice if other authors would use this check, too.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://www.wowace.com/projects/omen-threat-meter/
http://wow.curse.com/downloads/wow-addons/details/omen-threat-meter.aspx
http://www.wowinterface.com/downloads/info8459-OmenThreatMeter.html
Localization is still needed for most languages. deDE and frFR have been included. The curse version doesn't have frFR yet until I make a new beta/release tag.
Thanks.
Disclaimer: I'm not a native speaker, so there are bound to be errors. ;)
In the FAQ in Omen3 there are instructions for making Omen3 look like Omen2 by changing the Background and Borders to the Blizzard Tooltip style, the Background to black and the border color to blue.
That's awesome.
Except I can't figure out where those options are to change them.
I don't seem to have a mini-map icon to interact with Omen3 (it might be covered, but I con't find it) so I can only get to the options through pressing ESC, choosing Interface and finding Omen under the Add Ons tab.
I really miss the transparency and some of my guild mates are threatening to drop the add if we can't get that back.
Any clues what I'm doing wrong? Thanks.
Edit: Nevermind - logged out, logged back in and suddenly had more choices. =)
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumReally not sure if it'd be worth doing something like this in Omen3 given that there's alot less information to go around. But it certainly would be handy if Omen were able to detect these spell cast events all by itself. An Auto Mode feature would be neat, but long after the patch dust has settled, if at all. /hug!