GridLayoutByInstance Update (Attached below):
It is now properly compantible with TBC
It will now only update when the layout changes
You can now localise the... umm... name
For me, this makes it alot easier to see which status have priority. I've attached a zip with the (minor) changes to GridFrame.lua and GridStatus.lua as well as .diff files for both
Made a Layout that used TouristLib:GetInstanceGroupSize(GetRealZoneText()) to automaticly change the layout when you change zones (if you are not in an instance it will default to 40).
P.S: can you add GridLayout:SetModuleMixins("AceDebug-2.0", "AceEvent-2.0") and maybe a GridLayout.modulePrototype:UpdateLayout() function
When using GridStatus:SendStatusGained(name, status, priority, range, color, text, value, maxValue, texture), is it supposed to Register the status when the status isn't Registered?
It will send an unregistered status but it will not register an unregistered status.
Hmm, in my GridStatusMissingBuffs module it seemed to be registering unregistered statuses when I gained a buff in combat, to stop it I used UnitAffectingCombat("player") to make sure I didn't send GridStatus:SendStatusGained while in combat.
I've attached a slightly modified version of my GridStatusMissingBuffs without the in combat check. To reproduce:
# Make sure you don't have the buffs.
# Enter combat.
# Cast any buff that isn't a "Missing Buff" on you or anyone in your party.
I've also made some changes to your GridStatusMissingBuffs module.
Just fixed a few small bugs and it now Unregister / Registers SpecialEvents_UnitBuffGained and SpecialEvents_UnitBuffLost when entering / leaving combat.
I've created a Missing Buff module for Grid which will only when you are Out of Combat
When using GridStatus:SendStatusGained(name, status, priority, range, color, text, value, maxValue, texture), is it supposed to Register the status when the status isn't Registered?
Make a standalone addon that plugs into Grid which will allow you to drop your saved variables into it and load it up as the default settings so that you can easily share it.
I wrote this little plugin that (hopfully) does that :)
It's my first wow "mod" ever so i am happy about comments on it
don't forget to add the GridStatusTarget.lua to your Grid.toc
If you update to r15984, you can use the toc below to make GridStatusTarget a standalone module.
## Interface: 20000
## Title: GridStatusTarget |cff7fff7f -Ace2-|r
## Notes: Adds a status to Grid to show your target.
## Author: noha
## Version: 0.1
## Dependencies: Grid
## X-GridStatusModule: GridStatusTarget
GridStatusTarget.lua
I was attempting to make noha's module standalone per your instructions above, but I'm getting the following error (r15991):
It appears that the defaults are not being initialized for the standalone module although if it is placed in the Grid directory (and added to the toc), it works. Are the default variables supposed to be handled by a statement in the OnInitialize method such as self:RegisterStatus('alert_aggro', L["Aggro alert"], nil, true) or do we need to include AceDB and create a new instance for the module?
(Sorry if this question is noobish - this is the first time I've really played with coding in Ace.)
I'm getting the same error, I changed GridStatus.modulePrototype:OnInitialize() to:
function GridStatus.modulePrototype:OnInitialize()
GridStatus:Debug("Initializing "..self.name)
if self.db then
self.debugging = self.db.profile.debug
else
self.debugging = true
end
self.debugFrame = GridStatus.debugFrame
end
and noticed that in external modules :OnInitialize() is indeed being called before :RegisterModule()
An idea I would like to see is an option in WAU to download all the libraries. I know you can do this now with !!!StandaloneLibraries, but if for example there was a file added with the names of all the libraries or a seperate directory to store the libraries then WAU could easily download them and keep an updated list.
I really like this app, makes it really easy to update Ace Addons
Some Suggestions:
-> Add an option to save whether you have selected "Show Groups"
-> Allow you to sort addons when "Show Groups" is enabled (I like mine sorted alphabetically as its easier to find the addon i want)
-> I liked in v1.3 being able to right click on an addon from the list and choose to install it or uninstall it rather than having to go to "Edit Unmark All Addons" then check the addons i want then go to "File Uninstall Marked Addons".
-> An option for it to mark checked addons when it has recieved the addon list
Bugs:
-> When it tries to downloads an addon and it fails (e.g when it can't find the file cause it is incorrectly named) it seems to stop there and say "Update is complete" even though it hasn't completed.
0
It is now properly compantible with TBC
It will now only update when the layout changes
You can now localise the... umm... name
0
http://img329.imageshack.us/my.php?image=gridframeprioritysortpn6.png
For me, this makes it alot easier to see which status have priority. I've attached a zip with the (minor) changes to GridFrame.lua and GridStatus.lua as well as .diff files for both
0
0
0
P.S: can you add GridLayout:SetModuleMixins("AceDebug-2.0", "AceEvent-2.0") and maybe a GridLayout.modulePrototype:UpdateLayout() function
0
Hmm, in my GridStatusMissingBuffs module it seemed to be registering unregistered statuses when I gained a buff in combat, to stop it I used UnitAffectingCombat("player") to make sure I didn't send GridStatus:SendStatusGained while in combat.
I've attached a slightly modified version of my GridStatusMissingBuffs without the in combat check. To reproduce:
# Make sure you don't have the buffs.
# Enter combat.
# Cast any buff that isn't a "Missing Buff" on you or anyone in your party.
Edit: Nevermind, i'm abit confused
0
Just fixed a few small bugs and it now Unregister / Registers SpecialEvents_UnitBuffGained and SpecialEvents_UnitBuffLost when entering / leaving combat.
0
When using GridStatus:SendStatusGained(name, status, priority, range, color, text, value, maxValue, texture), is it supposed to Register the status when the status isn't Registered?
0
Make a standalone addon that plugs into Grid which will allow you to drop your saved variables into it and load it up as the default settings so that you can easily share it.
0
I'm getting the same error, I changed GridStatus.modulePrototype:OnInitialize() to:
and noticed that in external modules :OnInitialize() is indeed being called before :RegisterModule()
0
0
Some Suggestions:
-> Add an option to save whether you have selected "Show Groups"
-> Allow you to sort addons when "Show Groups" is enabled (I like mine sorted alphabetically as its easier to find the addon i want)
-> I liked in v1.3 being able to right click on an addon from the list and choose to install it or uninstall it rather than having to go to "Edit Unmark All Addons" then check the addons i want then go to "File Uninstall Marked Addons".
-> An option for it to mark checked addons when it has recieved the addon list
Bugs:
-> When it tries to downloads an addon and it fails (e.g when it can't find the file cause it is incorrectly named) it seems to stop there and say "Update is complete" even though it hasn't completed.
0
signed up, waiting for the reply
Also some more fixes:
Line 195 from:
to:
Line 209 from:
to:
Line 223 from:
to:
Line 237 from:
to:
Line 251 from:
to:
Line 281 from:
to:
As you can see, its all the same thing thats causing the error.
0
to:
and line 817 from:
to:
0