** Whenever I go link dead while in a raid, one of two things happen when I re-enter the game:
- All group frames overlap one another. Toggling the layout to something different and then back again usually fixes it.
- No unit frames display at all. A /console reloadui is necessary to fix it.
I noticed that the second, third and fourth members of the raid that are in the party no. 4 are not targettable. This issue occurred to everyone in the raid using Grid. I was using the r20780.
As this is a rather complex problem, I tend to reply with "sorry, not possible" instead, and I hope you now understand why. If you really want to help, please create a wiki topic for SecureRaidGroupHeader plus a discussion thread, get more developers to post there, work on possible suggestions for Blizzard, contact Esamynn, Cide and Iriel, let them know about these suggestions. I'll also be happy to email the suggestion to Slouken - once we really know what we'd want to suggest. Until then, we're stuck with what we have.
Great, thank you for the very thorough answer, maia. I will update the Wish List with a synopsis of this information in the very near future, and a link back here to your answer.
Unfortunately it looks like the "fix groups stacking on top of each other" fix actually bugged it out completely for me. I rarely had the stacking bug before but now I can't get them to NOT stack no matter what layout I use or what options. Using version r21114.
One feature I'd love to see is virtual groups, similar to the CTRA feature where you could get all 8 raid frames showing so they could be adjusted to your liking w/o being in a 40-person raid.
One feature I'd love to see is virtual groups, similar to the CTRA feature where you could get all 8 raid frames showing so they could be adjusted to your liking w/o being in a 40-person raid.
That's one feature(probably the only feature) I loved about CT Raid Frames, but if you want to make your raid UI(or test it out) just do what I do and enter AV(unless you have long AV queues) and set it up there :P
** Whenever I go link dead while in a raid, one of two things happen when I re-enter the game:
- All group frames overlap one another. Toggling the layout to something different and then back again usually fixes it.
- No unit frames display at all. A /console reloadui is necessary to fix it.
** Whenever I go link dead while in a raid, one of two things happen when I re-enter the game:
- All group frames overlap one another. Toggling the layout to something different and then back again usually fixes it.
- No unit frames display at all. A /console reloadui is necessary to fix it.
i have problem with Grid-r21205
i get this message, when i first start wow after installing grid.
"interface\addons\fubar\libs\aceOO-2.0\aceOO-2.0.lua:713: AceModuleCore-2.0 OnInstanceInit cannot be called twice"
and its okay, addon works and everything's okay but, when i exit the game, the same message appears, and most of my other ace addons like skinner, cycircled doesn't work.
List of the various configuration attributes
======================================================
nameList = [STRING] -- a comma separated list of player names (not used if 'groupFilter' is set)
groupFilter = [1-8, STRING] -- a comma seperated list of raid group numbers and/or uppercase class names
strictFiltering = [BOOLEAN] - if true, then characters must match both a group and a class from the groupFilter list
point = [STRING] -- a valid XML anchoring point (Default: "TOP")
xOffset = [NUMBER] -- the x-Offset to use when anchoring the unit buttons (Default: 0)
yOffset = [NUMBER] -- the y-Offset to use when anchoring the unit buttons (Default: 0)
sortMethod = ["INDEX", "NAME"] -- defines how the group is sorted (Default: "INDEX")
sortDir = ["ASC", "DESC"] -- defines the sort order (Default: "ASC")
template = [STRING] -- the XML template to use for the unit buttons
templateType = [STRING] - specifies the frame type of the managed subframes (Default: "Button")
Regarding these attributes for raid headers, does anyone know why there doesn't appear to be 'relativePoint' and 'frame' (relative frame) attributes? Kinda odd that those would be left out when they give you point and x,y offset attributes...
Regarding these attributes for raid headers, does anyone know why there doesn't appear to be 'relativePoint' and 'frame' (relative frame) attributes? Kinda odd that those would be left out when they give you point and x,y offset attributes...
Probably because that would allow easy repositioning in combat, which is exactly what Blizzard doesnt want.
But one of the latest version of Grid breaks with the "Incoming Heal-Indicator"... :-(
I ask myself why?
I'm unsure too - but as I currently don't play at all, I have a hard time fixing it. As the code has less than 100 lines, I can only hope someone else can add some debug code and find out why it's broken (I believe it is since the 2.0.1 patch).
I'm not sure if this is the problem I had, but I thought incoming heal indicator was broken, so I debugged it. My current version of Grid's incoming heal indicator works fine. Unless there's newer changes that broke it more, I posted a fix for the problem 6 days ago, in this very thread: http://www.wowace.com/forums/index.php?topic=2525.msg64762#msg64762
If there's another bug in there that's more recently introduced (meaning since the actual last Grid release, 'cause I don't do SVN versions :)), then I don't know about that.
The wiki has a link to post bugs, but the link is broken. Where should Grid bugs be posted, since it appears my previous post of this bug was missed?
Here's a longer explanation, and I'd appreciate if you'd create a wiki topic we could link to in future, especially as this problem isnt related to Grid but to code by blizzard (SecureRaidGroupHeader, contributed by Esamynn, Cide, and Iriel) that we have to use:
... see the post for full text ...
Well, the answer is simple. You cannot reposition these frames when in combat. So lets assume you're raiding AQ20 and have 2 priests, 2 shamans and one druid. You'd put the three frames underneath each other. Now what happenes when another priest joins? He'll overlap the next group, in other words you'll have two unit frames on top of each other. Even if you'd now say "hey, I can live with that - if I'm raiding, noone joins/leaves in combat" - well, you can't really delay the change of the units until the second you're out of combat. And, what would happen if you were in AV, where any other second someone leaves/joines? A big mess.
... more removed ...
Possible changes Blizzard could make:
... the changes removed ...
Have you noticed that every day, 1-3 people come here begging for the same 2-3 custom layouts? And the response is "Blizzard Secure Raid Headers don't allow it."
Sure, and without the Blizzard Secure Raid Headers, you can't reposition in combat.
So what? How about a best-effort?
Can't you just write 40 buttons. Not even using the raid headers. Those buttons can look any way you want them to, and each possible click on them can do anything you want it to. Target, cast, whatever. As long as you set it up before combat.
So every single layout these people ask for would work. It would just have some weird annoyances if people join or leave while you're in combat, since Blizzard's frames update during combat, and yours can't. So what? Who cares? Your example of frames overlapping if a warrior leaves and a priest joins would be annoying, yes. So why would you implement it that way? Why not have 40 buttons, set up to display the way we want them to display, and sorted the way we want them sorted pre-combat. Any one of the ways people want them -- sorted by class forced into a 5x8 (so allow overflow), or rows by class sorted by name, or anything. Then if your priest leaves and is replaced by a warrior during combat, then the warrior is stuck in the priest group on your interface in the rwong alphabetical order until the combat ends. That's really not that bad of a situation to be in. In PvP, it's not like you're expecting a casual clean interface -- I make anyone who's out of range in PvP go 5% alpha anyway, so if the warrior in the priest group just joined? I won't even see that it's not the priest any more until long after I drop out of combat for a second.
And obviously, when I'm rocking Naxx? People don't join and leave during combat. Unless something is going very, very wrong. And if something is that wrong, hey! who cares! Once the wipe's over, my interface'll update. :)
I mean, I can accept the argument "With the way Grid is set up right now, that would be a lot of work and really annoying to maintain." But I have yet to see an argument that actually explains to me why it's not possible to have a 100% customizable layout option. And for people who really don't want to ever see a warrior in the middle of the priest group under any circumstances, there's still the sorting options that are available right now.
-x
PS theoretically, since I haven't actually *written* a grid-like mod that does what I was saying is possible, I could be wrong, and if so, I'd like to know why... what part of what I described isn't possible? :) Thanks!
PPS I'm a fan of the current sorting systems, myself, and would never use the ideas I described, I only ask this 'cause it seems like it should be possible given everything I know about the secure system, and despite tons of requests for it, there seems to be this outright denial of it even being possible, so I'm interested in knowing why it's impossible, or why you say it is. :)
How about because I feel that's the wrong way to do it and that it's not worth the trouble? Anyone who feels differently is more than welcome to replace GridLayout with their own version.
I am using Grid since some weeks and I can't understand what trouble people have with the sort options.
Personaly, I use Grid for healing and decurse (I am a Paladin), so my settings are very simple:
- Class order
- Show debuff
- Show healing in progress (when working :P)
- Alpha set to 10% if not in range/death/offline
This way, I can heal fast warriors, druids, priest, ... in my range and I really don't care about the name of the guy I am healing.
This mod is great and fast, more options you will have, more slow and useless it will be.
Now if someone really need a sorted frames system, why not create an other addOn or a grid option that will simply parse your raid members and order them by name (nameList = [STRING]), you will simply have to do it manualy everytime someone join/leave the group and you are out of combat. This must be faster to develop and not change the way Grid is working if I am not wrong.
-= I was a bit confuse with this mod when I started to use it - but now, I love it - thanks great team =-
Hmmm did you something special to Grid since yesterday? After updating my ace-collection my memory increasing rate when in raid and not fighting decreased from 18 kb to 0,9 kb - WOW very nice work ideed :D :)
I dont know is this Grid problem. But every time I enter AV when raid is not full and ppl are joining i have this error:
Error: table index is nil
File: Interface\FrameXML\SecureTemplates.lua
Line: 816
Count: 4
I dont know is this Grid problem. But every time I enter AV when raid is not full and ppl are joining i have this error:
Error: table index is nil
File: Interface\FrameXML\SecureTemplates.lua
Line: 816
Count: 4
What is this ?
A question that was asked and answered on the previous page!
Hmmm did you something special to Grid since yesterday? After updating my ace-collection my memory increasing rate when in raid and not fighting decreased from 18 kb to 0,9 kb - WOW very nice work ideed :D :)
I believe several optimizations have been done to RosterLib to use the new garbage system in LUA 5.1.
Quote from Pastamancer »
A question that was asked and answered on the previous page!
Now it is the latest addition to the FAQ! It will not be answered again.
:(
As far as layouts go, I think it would be better to address the constraining issues to Slouken and see what everyone can come up with, rather than going behind what they're trying to provide for us. I'm sure if something can be done within Blizzard's desired restrains, Slouken will make it so. If the Secure stuff isn't quite doing what we want it to, and what we want is reasonable, it's in everyone's best interest to point that out to Blizzard.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis should be fixed as of r21114.
That's one feature(probably the only feature) I loved about CT Raid Frames, but if you want to make your raid UI(or test it out) just do what I do and enter AV(unless you have long AV queues) and set it up there :P
Thank you!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumPlease test!
i get this message, when i first start wow after installing grid.
"interface\addons\fubar\libs\aceOO-2.0\aceOO-2.0.lua:713: AceModuleCore-2.0 OnInstanceInit cannot be called twice"
and its okay, addon works and everything's okay but, when i exit the game, the same message appears, and most of my other ace addons like skinner, cycircled doesn't work.
Regarding these attributes for raid headers, does anyone know why there doesn't appear to be 'relativePoint' and 'frame' (relative frame) attributes? Kinda odd that those would be left out when they give you point and x,y offset attributes...
Probably because that would allow easy repositioning in combat, which is exactly what Blizzard doesnt want.
I'm not sure if this is the problem I had, but I thought incoming heal indicator was broken, so I debugged it. My current version of Grid's incoming heal indicator works fine. Unless there's newer changes that broke it more, I posted a fix for the problem 6 days ago, in this very thread:
http://www.wowace.com/forums/index.php?topic=2525.msg64762#msg64762
If there's another bug in there that's more recently introduced (meaning since the actual last Grid release, 'cause I don't do SVN versions :)), then I don't know about that.
The wiki has a link to post bugs, but the link is broken. Where should Grid bugs be posted, since it appears my previous post of this bug was missed?
-x
Have you noticed that every day, 1-3 people come here begging for the same 2-3 custom layouts? And the response is "Blizzard Secure Raid Headers don't allow it."
Sure, and without the Blizzard Secure Raid Headers, you can't reposition in combat.
So what? How about a best-effort?
Can't you just write 40 buttons. Not even using the raid headers. Those buttons can look any way you want them to, and each possible click on them can do anything you want it to. Target, cast, whatever. As long as you set it up before combat.
So every single layout these people ask for would work. It would just have some weird annoyances if people join or leave while you're in combat, since Blizzard's frames update during combat, and yours can't. So what? Who cares? Your example of frames overlapping if a warrior leaves and a priest joins would be annoying, yes. So why would you implement it that way? Why not have 40 buttons, set up to display the way we want them to display, and sorted the way we want them sorted pre-combat. Any one of the ways people want them -- sorted by class forced into a 5x8 (so allow overflow), or rows by class sorted by name, or anything. Then if your priest leaves and is replaced by a warrior during combat, then the warrior is stuck in the priest group on your interface in the rwong alphabetical order until the combat ends. That's really not that bad of a situation to be in. In PvP, it's not like you're expecting a casual clean interface -- I make anyone who's out of range in PvP go 5% alpha anyway, so if the warrior in the priest group just joined? I won't even see that it's not the priest any more until long after I drop out of combat for a second.
And obviously, when I'm rocking Naxx? People don't join and leave during combat. Unless something is going very, very wrong. And if something is that wrong, hey! who cares! Once the wipe's over, my interface'll update. :)
I mean, I can accept the argument "With the way Grid is set up right now, that would be a lot of work and really annoying to maintain." But I have yet to see an argument that actually explains to me why it's not possible to have a 100% customizable layout option. And for people who really don't want to ever see a warrior in the middle of the priest group under any circumstances, there's still the sorting options that are available right now.
-x
PS theoretically, since I haven't actually *written* a grid-like mod that does what I was saying is possible, I could be wrong, and if so, I'd like to know why... what part of what I described isn't possible? :) Thanks!
PPS I'm a fan of the current sorting systems, myself, and would never use the ideas I described, I only ask this 'cause it seems like it should be possible given everything I know about the secure system, and despite tons of requests for it, there seems to be this outright denial of it even being possible, so I'm interested in knowing why it's impossible, or why you say it is. :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHow about because I feel that's the wrong way to do it and that it's not worth the trouble? Anyone who feels differently is more than welcome to replace GridLayout with their own version.
Personaly, I use Grid for healing and decurse (I am a Paladin), so my settings are very simple:
- Class order
- Show debuff
- Show healing in progress (when working :P)
- Alpha set to 10% if not in range/death/offline
This way, I can heal fast warriors, druids, priest, ... in my range and I really don't care about the name of the guy I am healing.
This mod is great and fast, more options you will have, more slow and useless it will be.
Now if someone really need a sorted frames system, why not create an other addOn or a grid option that will simply parse your raid members and order them by name (nameList = [STRING]), you will simply have to do it manualy everytime someone join/leave the group and you are out of combat. This must be faster to develop and not change the way Grid is working if I am not wrong.
-= I was a bit confuse with this mod when I started to use it - but now, I love it - thanks great team =-
Error: table index is nil
File: Interface\FrameXML\SecureTemplates.lua
Line: 816
Count: 4
What is this ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumA question that was asked and answered on the previous page!
It has also been asked and asked and answered and asked and answered and asked and answered many times before.
Now it is the latest addition to the FAQ! It will not be answered again.
I believe several optimizations have been done to RosterLib to use the new garbage system in LUA 5.1.
:(
As far as layouts go, I think it would be better to address the constraining issues to Slouken and see what everyone can come up with, rather than going behind what they're trying to provide for us. I'm sure if something can be done within Blizzard's desired restrains, Slouken will make it so. If the Secure stuff isn't quite doing what we want it to, and what we want is reasonable, it's in everyone's best interest to point that out to Blizzard.