You're just not in the right spot. Try increasing the padding setting; this will give you more of an area around the unit frames you can click on to drag the layout while it's unlocked.
Hi, been awhile since ive been to the Ace Forums but wanted to say thanks to all the modders who create these awesome addons. im a resto druid and i LOVED grid with all its lil plugins pre patch. but now im having problems post patch. its set in the same place for the most part, but i cant seem to unlock the window to move it. the MiniMap button isnt working and the /grid commands arent even letting me press execute with a /grid (anything). i usually update from Curse. should i uninstall then reinstall? or is it cause i dont have Ace 3 installed?
You never need a standalone copy of Ace3, unless an addon's author did not properly package his addon. The whole point of the Ace3 family of libraries is that they are embeddable, so that users don't have to keep track of installing them separately.
That said, if you've already double-checked that you have the latest release version, and the problem still happens when Grid is the only addon enabled, then:
I'd like to try my hands at making a module but I don't know where to start. I've looked at the doc in linked with the addon page and some of the modules out but I just can't seam to grasp what is needed by the Grid framework and what is added by the module. Any pointers?
I have a question, i want to use self.core:SendStatusGained, how can I send the parameter that will be used for SetTexCoord with my texture? I want to use Blizzard texture but the one I need requires a SetTexCoord.
I saw those and I saw no ways to pass texleft,texright,textop,texbottom (the parameters from SetTexCoord). In fact, I see nowhere in Grid code where SetTexCoord is based on parameters set by a module.
What I wanted to do was to use "Interface\\LFGFrame\\UI-LFG-ICON-PORTRAITROLES" for texture and then do something like tex:SetTextCoord(0, 19/64, 22/64, 41/64) for tank, tex:SetTextCoord(20/64, 39/64, 1/64, 20/64) for healer and tex:SetTextCoord(0.25, 0.5, 0, 1) for DPS. Blizz even have the GetTexCoordsForRoleSmall to help get the texture coord right.
I think I'll just open a ticket for a mew feature but there is no hurry. While searching for the best ways to do what I wanted I found GridStatusDungeonRole that already do it. The author, who is better then me with tinkering with Blizzard graphics, already has extracted them and converted them in .tga files that can be used directly by Grid.
We can't have direct access to the texture object since the parameter are passed as a message so it would have to be something like more parameters for SendStatusGained, a new optional structure for the tex parameter or embeded the parameters in the tex sting a bit like it's done for the |T escape sequence e.g. "texture_path:texleft,texright,textop,texbottom".
Thanks for your help Phanx, I'll fill the feature request and you can decide whatever you want to do about this no rush.
There is no way to pass texture coordinates; if you dig around in the old thread, you'll see that was requested a long time ago, and Pasta decided not to add it. I don't recall the reasons offhand. I'll keep it in mind for the future, but don't expect it any time soon.
There is no way to pass texture coordinates; if you dig around in the old thread, you'll see that was requested a long time ago, and Pasta decided not to add it. I don't recall the reasons offhand. I'll keep it in mind for the future, but don't expect it any time soon.
That's OK with me. I understand that is really not a priority. I've created a ticket for it so you'll have a reference if you ever decide to do something about it.
1x Grid-1.40000.1370\GridCore.lua:168: Cannot find a library instance of "LibDualSpec-1.0".
Ace3-Release-r971\LibStub\LibStub.lua:23: in function `LibStub'
Grid-1.40000.1370\GridCore.lua:168: in function <Grid\GridCore.lua:159>
<in C code>: ?
<string>:"safecall Dispatcher[1]":3: in function <[string "safecall Dispatcher[1]"]:3>
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):510: in function `InitializeAddon'
AceAddon-3.0-5 (Ace3):622: in function <Ace3\AceAddon-3.0\AceAddon-3.0.lua:615>
I have some modifications for the GridStatusAuras module that add the ability to independently map the duration and the stack count of buffs/debuffs onto the text and color statuses. The changes aren't too extensive (they are mostly code additions that are independent of the existing code), but I'm unsure how to submit the modifications.
I took a look at existing tickets for Grid and found 209 - Support for # of charges of a buff. The commentary on the ticket was instructive so I took a different approach.
For each aura tracked by GridStatusAuras, there are two new suboptions to manage settings for a duration status and a stack count status. For the duration status, there are 2 threshold settings and 3 colors. When duration is mapped onto the color status, then the status changes colors depending on which threshold the remaining duration is under. Similarly for the stack count status, which when mapped onto the color status will change colors depending on which threshold the stack count is under.
If any of the aura statuses map duration onto either text or color, then a repeating timer is set up to refresh the Grid units based on a settable refresh interval. If duration isn't used for any aura that's currently active on Grid units, then the timer is removed. Each aura status has a refresh interval setting, and the smallest interval used by active auras on the Grid units is chosen for the repeating timer.
The main purpose of the changes is to allow tracking of HoT and debuff timers using Grid text indicators. For most simple HoTs, just mapping duration to the text status is sufficient, but something like Lifebloom can have the duration mapped to text and stack count mapped to color to display both pieces of information on the same indicator. For buffs with charges, e.g. shaman shields, the stack count can be mapped to both the text and color statuses so that a warning color is used when a minimum threshold, e.g. 1 charge remaining, is reached.
/gridnot working
It seems this is due to two files in the lib folder, and even when I replace them the game deletes them at some point, whether logging in or out... they just vanish.
This happens with pitbull as well for the same files in the lib dualspec folder.
If addon files are disappearing, then either the Curse Client is deleting them, or there is something wrong with your hard drive and/or operating system installation. If you're running the Curse Client, try downloading the addons you're having trouble with by hand, and not running the Curse Client for a few game sessions. If the files stop disappearing when you stop running the Curse Client, post on the Curse Client support site. If the files still disappear, I don't know. Reinstall Windows or buy a new hard drive, I guess.
In any case, Grid (or any other addon) cannot delete files from your hard drive, so I can't really help you beyond that.
That said, if you've already double-checked that you have the latest release version, and the problem still happens when Grid is the only addon enabled, then:
1. Install !BugGrabber and BugSack.
2. Post the error(s) BugSack shows that mention Grid on the ticket tracker.
http://paste.wowace.com/2673/
I have a question, i want to use self.core:SendStatusGained, how can I send the parameter that will be used for SetTexCoord with my texture? I want to use Blizzard texture but the one I need requires a SetTexCoord.
TIA
I saw those and I saw no ways to pass texleft,texright,textop,texbottom (the parameters from SetTexCoord). In fact, I see nowhere in Grid code where SetTexCoord is based on parameters set by a module.
What I wanted to do was to use "Interface\\LFGFrame\\UI-LFG-ICON-PORTRAITROLES" for texture and then do something like tex:SetTextCoord(0, 19/64, 22/64, 41/64) for tank, tex:SetTextCoord(20/64, 39/64, 1/64, 20/64) for healer and tex:SetTextCoord(0.25, 0.5, 0, 1) for DPS. Blizz even have the GetTexCoordsForRoleSmall to help get the texture coord right.
I think I'll just open a ticket for a mew feature but there is no hurry. While searching for the best ways to do what I wanted I found GridStatusDungeonRole that already do it. The author, who is better then me with tinkering with Blizzard graphics, already has extracted them and converted them in .tga files that can be used directly by Grid.
We can't have direct access to the texture object since the parameter are passed as a message so it would have to be something like more parameters for SendStatusGained, a new optional structure for the tex parameter or embeded the parameters in the tex sting a bit like it's done for the |T escape sequence e.g. "texture_path:texleft,texright,textop,texbottom".
Thanks for your help Phanx, I'll fill the feature request and you can decide whatever you want to do about this no rush.
That's OK with me. I understand that is really not a priority. I've created a ticket for it so you'll have a reference if you ever decide to do something about it.
1x Grid-1.40000.1370\GridCore.lua:168: Cannot find a library instance of "LibDualSpec-1.0".
Ace3-Release-r971\LibStub\LibStub.lua:23: in function `LibStub'
Grid-1.40000.1370\GridCore.lua:168: in function <Grid\GridCore.lua:159>
<in C code>: ?
<string>:"safecall Dispatcher[1]":3: in function <[string "safecall Dispatcher[1]"]:3>
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):510: in function `InitializeAddon'
AceAddon-3.0-5 (Ace3):622: in function <Ace3\AceAddon-3.0\AceAddon-3.0.lua:615>
---
I took a look at existing tickets for Grid and found 209 - Support for # of charges of a buff. The commentary on the ticket was instructive so I took a different approach.
For each aura tracked by GridStatusAuras, there are two new suboptions to manage settings for a duration status and a stack count status. For the duration status, there are 2 threshold settings and 3 colors. When duration is mapped onto the color status, then the status changes colors depending on which threshold the remaining duration is under. Similarly for the stack count status, which when mapped onto the color status will change colors depending on which threshold the stack count is under.
If any of the aura statuses map duration onto either text or color, then a repeating timer is set up to refresh the Grid units based on a settable refresh interval. If duration isn't used for any aura that's currently active on Grid units, then the timer is removed. Each aura status has a refresh interval setting, and the smallest interval used by active auras on the Grid units is chosen for the repeating timer.
The main purpose of the changes is to allow tracking of HoT and debuff timers using Grid text indicators. For most simple HoTs, just mapping duration to the text status is sufficient, but something like Lifebloom can have the duration mapped to text and stack count mapped to color to display both pieces of information on the same indicator. For buffs with charges, e.g. shaman shields, the stack count can be mapped to both the text and color statuses so that a warning color is used when a minimum threshold, e.g. 1 charge remaining, is reached.
Reinstall the addon. I just manually downloaded a fresh copy of the zip, and LibDualSpec-1.0 is correctly included and referenced in the TOC.
Create a unified diff file (TortoiseSVN can do this) and attach it to a new Patch ticket, and I'll take a look.
http://www.wowace.com/addons/grid/create-ticket/
It seems this is due to two files in the lib folder, and even when I replace them the game deletes them at some point, whether logging in or out... they just vanish.
This happens with pitbull as well for the same files in the lib dualspec folder.
In any case, Grid (or any other addon) cannot delete files from your hard drive, so I can't really help you beyond that.