LibFubarPlugin-Mod-3.0 is copied, not externalized, to both MagicTargets and Omen and they are identical. Likely the issue is simply that MagicTargets didn't have FuBar as an optional dependency.
As for LibLogger - it's a minimalistic logging library I wrote. It's not going to "hurt" anything if it isn't used.
The one included with Omen _is_ "externalized"; its copied, like most libraries are, to a separate folder in a "\libs" subfolder. And then only if you do not "Omit Externals" (if downloading with a SVN client) or the equivalent with WAU or similar. Unlike MagicTargets, where its downloaded to the root mod folder in all circumstances.
But looking into it further and doing a file compare of the two versions of LibFubarPlugin-Mod-3.0, yes, there are only two minor file differences. The differences between the one included with Omen (if you download externals) and MagicTargets are the following two lines:
Line 3: Revision: $Rev: 75670 $
Line 12: local MINOR_VERSION = tonumber(("$Revision: 75670 $"):match("(%d+)")) - 60000
for MagicTargets vs.
Line 3: Revision: $Rev: 74211 $
Line 12: local MINOR_VERSION = tonumber(("$Revision: 74211 $"):match("(%d+)")) - 60000
for Omen.
The rest of the code is identical. Regardless, the error was solved by deleting the LibFubarPlugin-Mod-3.0.lua file included with MagicTargets and letting it use the one loading with Omen.
For LibLogger, why have it loading (taking up time & memory, albeit small) if it is not used? :)
It is in fact not. Look again. The versions, obviously, are different because they are different copies in SVN. Just because a file is in a directory "Libs" doesn't make it external. Since the hacked fubar plugin is on a branch only, it is being manually copied to avoid the headaches associated with externalizing to a branch. Want proof?
So again, the files are identical and that is not the source of the problem. The source is the plugin failing to load properly due to load order and lack of dependencies, just as I stated in my original post.
As for LibLogger, which is a logging library of minimalistic propotions, I sure hope your computer doesn't suffer from the 5 KB of memory it's using. I also remember when my computer only had 48KB total memory and that amount of data mattered. That said, right now it's not really used that much in MagicTargets for sure, but complaining about it using resources is somewhat unnecessary.
P.S. I've removed LibLogger as a dependency. Might change if I use it more but alas. It'll still be embedded if found during initialization.
Displaying the target for each mob would be excellent for tanking trash in heroics. As a tank it's always challenging to see when someone pulled aggro when trying to keep 3+ mobs on me.
Is it possible to set the focus frame to a mob that's detected as untanked by MagicTargets, if the focus isn't already set?
Displaying the target for each mob would be excellent for tanking trash in heroics. As a tank it's always challenging to see when someone pulled aggro when trying to keep 3+ mobs on me.
Is it possible to set the focus frame to a mob that's detected as untanked by MagicTargets, if the focus isn't already set?
I don't think addons can choose to target (or focus target) an arbitrary unit.
Yeah targeting unfortunately doesn't work. I still have lose plans of making a companion addon, plugin or extra feature that shows a grid of all raidXtarget/partyXtarget, with at least raid symbol, of any, and blue/green/red color (or whatever colors you configured). It's not as handy as 4 bars, but if someone is targeting a mob that's not tanked it will at least be quick to target it.
Yeah targeting unfortunately doesn't work. I still have lose plans of making a companion addon, plugin or extra feature that shows a grid of all raidXtarget/partyXtarget, with at least raid symbol, of any, and blue/green/red color (or whatever colors you configured). It's not as handy as 4 bars, but if someone is targeting a mob that's not tanked it will at least be quick to target it.
Sounds worth investigating at least, although I think it would be challenging to make something usable. Maybe something with colors and/or names/numbers.
Currently seing an error when showing the anchor, moving it and then hiding it again. The result of which is that the new position is not being saved. This is on live with addons updated via WAU earlier this evening.
Swatter debug as an attachment due to excessive addon list =)
The one included with Omen _is_ "externalized"; its copied, like most libraries are, to a separate folder in a "\libs" subfolder. And then only if you do not "Omit Externals" (if downloading with a SVN client) or the equivalent with WAU or similar. Unlike MagicTargets, where its downloaded to the root mod folder in all circumstances.
But looking into it further and doing a file compare of the two versions of LibFubarPlugin-Mod-3.0, yes, there are only two minor file differences. The differences between the one included with Omen (if you download externals) and MagicTargets are the following two lines:
Line 3: Revision: $Rev: 75670 $
Line 12: local MINOR_VERSION = tonumber(("$Revision: 75670 $"):match("(%d+)")) - 60000
for MagicTargets vs.
Line 3: Revision: $Rev: 74211 $
Line 12: local MINOR_VERSION = tonumber(("$Revision: 74211 $"):match("(%d+)")) - 60000
for Omen.
The rest of the code is identical. Regardless, the error was solved by deleting the LibFubarPlugin-Mod-3.0.lua file included with MagicTargets and letting it use the one loading with Omen.
For LibLogger, why have it loading (taking up time & memory, albeit small) if it is not used? :)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://svn.wowace.com/wowace/trunk/Omen/Libs/
http://svn.wowace.com/wowace/trunk/FuBar_WhoRollFu/Libs/
http://fish.wowace.com/browse/WowAce/trunk/Omen/Libs/LibFuBarPlugin-3.0
So again, the files are identical and that is not the source of the problem. The source is the plugin failing to load properly due to load order and lack of dependencies, just as I stated in my original post.
As for LibLogger, which is a logging library of minimalistic propotions, I sure hope your computer doesn't suffer from the 5 KB of memory it's using. I also remember when my computer only had 48KB total memory and that amount of data mattered. That said, right now it's not really used that much in MagicTargets for sure, but complaining about it using resources is somewhat unnecessary.
P.S. I've removed LibLogger as a dependency. Might change if I use it more but alas. It'll still be embedded if found during initialization.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIs it possible to set the focus frame to a mob that's detected as untanked by MagicTargets, if the focus isn't already set?
I don't think addons can choose to target (or focus target) an arbitrary unit.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSounds worth investigating at least, although I think it would be challenging to make something usable. Maybe something with colors and/or names/numbers.
Swatter debug as an attachment due to excessive addon list =)