Thank you. I've just about got my status module working. One of the things the module does is change the status color based on the unit's position. There was a bit of unexpected behaviour because created one color table, used it as an upvalue, populated it and sent it to GridStatus:SendStatusGained. The code in SendStatusGained goes:
if cached and
cached.priority == priority and
cached.range == range and
cached.color == color and
...
This checks whether the color table is the same table reference as the cached one and not whether the actual colors are the same.
Would this be considered an issue at your end, or is dynamic color changing not common enough to be worth worrying about? I'm formulating a solution at my end which involves my first use of weak tables, which is sort of exciting :)
Hmm on second thought seeing your question is about status I know that implementation has changed a fair bit recently concerning those... The old.wowace.com wiki may not be very helpful. I don't maintain any status plugin so I cannot be more helpful than that.
This checks whether the color table is the same table reference as the cached one and not whether the actual colors are the same.
Would this be considered an issue at your end, or is dynamic color changing not common enough to be worth worrying about? I'm formulating a solution at my end which involves my first use of weak tables, which is sort of exciting :)
It's intended. You should have one table per color rather than one table per unit. If you're changing color based on range you have what... 4-5 different colors?
In AB the unit name is colored depending on the status of the flag they're near, so 5 colors (more if you factor in alpha). In WSG units are red at the horde end and blue at the alliance end. In the middle the unit's color changes smoothly from blue to grey to red depending on where they are (see picture).
At the moment these colors are just passed directly to SetTextColor(). I've done a solution where colors are stored in a weak table and are collected when Grid is finished with them (lifted wholesale from Programming in Lua 17.1). This would create a maximum of one new table per OnUpdate (my addon processes one unit per OnUpdate). The alternative would be to round the color numbers to the nearest 0.05 or whatever, which would produce fewer discrete colors and tables, and fewer update events for Grid. I'm not sure if this is necessary though.
Hmmm... I though that the and could be used in XML. Is there a problem with the way the packager works ?
The packager does support the equivalent tags for XML, but it's a waste of time to load a whole extra file (embeds.xml) when 100% of its contents will be ignored anyway. Simpler and more efficient all around to just reference the libs in the TOC and add the no-lib-strip tags there.
But since one of the last wowmatrix updates, this doesn't work any longer.
1. There are numerous threads on this and other forrums explaining in great detail why WoWMatrix is bad. Basically, it steals bandwidth from the sites who actually host the addons, prevents those sites from recouping any operating costs through ad revenue, does not respect addon authors' legal rights, and only recently started crediting authors by name after sustained campaigning by many addon authors. There are other ways to get your addons easily that are not fraught with such legal and ethical problems. If you really must use this parasitic program, you'd be best off not mentioning it in the future when you post asking for help from addon authors, especially when you're posting on one of the sites that WoWMatrix steals bandwidth from.
2. The change you describe was actually made months ago, along with several other major changes to Grid's internal workings. Unless you are a Lua programmer, there is no way to get the previous layout back. This was changed because most people disliked having everything in one row or column.
Is there a way to modify the size of each unit frame within the grid? I know I did it a long time ago when I was trying out grid/clique, but no longer have my old settings and can't remember how I did it.
Also, is there a way to search for text within a thread in this forum? I mean this thread alone is showing as 282 pages... I don't mind searching for my answer, but I'm leery of manually digging through 250+ pages of posts to find it. =/
Is there a way to modify the size of each unit frame within the grid? I know I did it a long time ago when I was trying out grid/clique, but no longer have my old settings and can't remember how I did it.
Also, is there a way to search for text within a thread in this forum? I mean this thread alone is showing as 282 pages... I don't mind searching for my answer, but I'm leery of manually digging through 250+ pages of posts to find it. =/
On the search page you select "show result as [ ] thread [ ] post"
On the search page you select "show result as [ ] thread [ ] post"
Thanks, that has helped me in searching a lot. Though I still haven't been able to find anything in the past hour or so on how to make grid a little less grid and little more rectangles.
Thanks, that has helped me in searching a lot. Though I still haven't been able to find anything in the past hour or so on how to make grid a little less grid and little more rectangles.
I'm not sure if this is a Grid problem or a Recount problem but figured I'd post to find out if either author knew what might be causing it.
First to preface, I use Recount as Load on Demand so it doesn't memory hog in bgs/arena/etc. if I don't care about stats, but do load it for raids. Grid I always have load at log in. (Grid r1174, Recount r1039)
I get this error when I load Recount (w/ libs embedded or w/o) and Grid has frames up on the screen. No error when it's not displaying anything. It doesn't seem to mess anything up that I can tell, but then I do get random black frames on Grid occasionally (until hp is updated from a buff or heal/dmg) and was wondering if this had anything to do with it.
I posted this on Recount's thread as well to see if anyone knows what might be causing this error and thanks for your time if you can come up with anything.
P.S.- Is the black frames every now and then on Grid related to something else or might this be causing that?
This is a likely caused by your Grod settings specifying a font that isn't yet available when Grid initially loads... since you mention Recount, if you're using the font "ABF", that's your problem. ABF is bundled with Recount, but on NTFS systems (most modern Windows systems) addons are loaded alphabetically, so when Grid loads, Recount isn't yet loaded, and ABF hasn't yet been registered with LibSharedMedia-3.0.
Solutions:
Install the addon "SharedMedia" and add ABF to it if it's not already included. This will give you many more fonts and statusbar textures for use in all addons, and is OptDep'ed by Grid, so it will load before Grid.
Add Recount to Grid's OptDeps. You'll need to redo this every time you update Grid.
P.S.- Is the black frames every now and then on Grid related to something else or might this be causing that?
While it's possible that the font error causes black frames, it's unlikely. You can easily check though, by setting your font to Friz Quadrata or Arial Narrow (or another font that's guaranteed to be available when Grid loads) and see if you still get black frames. My guess though, is that you either have corruption in your saved variables, or have something "bad" set to use the Health Bar Color indicator, or have a plugin causing problems. Try playing with just Grid and no GridWhatever plugins, and see if the black frames occur. If they don't, it's a plugin problem; post a list of plugins you're using.
There is also the problem of party frame creation while in combat. If someone joins your party/raid while you are in combat (happens a lot in BGs) addons that dynamically create frames for them can error typically leading to black frames.
In my setup this affects both aguf and grid, and it's a blizz issue. Not sure if it's fixed on the PTR yet.
Ok, tested with a new copy of the latest release version of SharedMediaLib3.0 and got the same error (I was already using this mod). Checked the font Grid was using and it's using FrizQuadrataTT, so not ABF. Checked to see if it was my Grid Saved Vars by deleting them and it still gave the same error regardless of any of the above.
Adding Recount to optional dependencies for Grid makes it auto load at startup despite being labeled for LOD, which kind of defeats the purpose of it being LOD. However, doing that did make no errors appear on login.
I run no plugins for Grid, just the bread and butter basic raidframe. It is, however, running unembedded, as are most of my mods. Haven't tested fully if the saved vars deletion will remove the black frames, but setting it up now after deleting the vars and will find out tonight.
Thanks again for your help, and would appreciate any other suggestions for keeping Recount LOD, but not have that error.
Edit: Oh, also of note, I changed Recount's font to FrizQuadrataTT as well and am still getting the error when loading it.
Adding Recount to optional dependencies for Grid makes it auto load at startup despite being labeled for LOD, which kind of defeats the purpose of it being LOD. However, doing that did make no errors appear on login.
Neither Recount nor Grid are LoD, so I have no idea what you're talking about here... if you've modified either addon from its official version, you're pretty much on your own as far as conflicts between addons go.
Try logging in with only Grid enabled, and changing the font from its current setting to something else that's available when only Grid is enabled. The only choices that should be available there are Arial Narrow, Friz Quadrata TT, Morpheus, and Skurri. Even if it's already set to one of those, change it. Now log out and back in, or reload your UI, and see if the error still occurs. If not, enable Recount too, and see if the error still occurs. If not, enable the rest of your addons, and see if the error still occurs.
If you're using modified versions, try backing those up and downloading copies of the official versions. If this makes the problem go away, then the problem is something you caused, and you should be able to narrow it down from there.
Also, if you're using a modified version of an addon, you should always mention that when posting a bug report. Otherwise, the author (and users who are trying to help) are likely to spend a lot of time looking in the wrong place for a solution to your problem. Reporting that "Line 47 in Version 2.8b gives me this error" is worse than no error message at all when Line 47 in Version 2.8b is actually a blank line, or a line that couldn't possibly generate the error you posted.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Thank you. I've just about got my status module working. One of the things the module does is change the status color based on the unit's position. There was a bit of unexpected behaviour because created one color table, used it as an upvalue, populated it and sent it to GridStatus:SendStatusGained. The code in SendStatusGained goes:
if cached and cached.priority == priority and cached.range == range and cached.color == color and...This checks whether the color table is the same table reference as the cached one and not whether the actual colors are the same.
Would this be considered an issue at your end, or is dynamic color changing not common enough to be worth worrying about? I'm formulating a solution at my end which involves my first use of weak tables, which is sort of exciting :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's intended. You should have one table per color rather than one table per unit. If you're changing color based on range you have what... 4-5 different colors?
At the moment these colors are just passed directly to SetTextColor(). I've done a solution where colors are stored in a weak table and are collected when Grid is finished with them (lifted wholesale from Programming in Lua 17.1). This would create a maximum of one new table per OnUpdate (my addon processes one unit per OnUpdate). The alternative would be to round the color numbers to the nearest 0.05 or whatever, which would produce fewer discrete colors and tables, and fewer update events for Grid. I'm not sure if this is necessary though.
The packager does support the equivalent tags for XML, but it's a waste of time to load a whole extra file (embeds.xml) when 100% of its contents will be ignored anyway. Simpler and more efficient all around to just reference the libs in the TOC and add the no-lib-strip tags there.
my Grid used to show Pets in the same row as the owner, like this:
hunter | warlock | druid | paladin | mage | pet1 | pet2
But since one of the last wowmatrix updates, this doesn't work any longer.
Instead, I have now 2 rows:
hunter | warlock | druid | paladin | mage
pet1 | pet2
Does anybody know how I can change this to the old behavior?
wowmatrix is evil! Yes it is!
1. There are numerous threads on this and other forrums explaining in great detail why WoWMatrix is bad. Basically, it steals bandwidth from the sites who actually host the addons, prevents those sites from recouping any operating costs through ad revenue, does not respect addon authors' legal rights, and only recently started crediting authors by name after sustained campaigning by many addon authors. There are other ways to get your addons easily that are not fraught with such legal and ethical problems. If you really must use this parasitic program, you'd be best off not mentioning it in the future when you post asking for help from addon authors, especially when you're posting on one of the sites that WoWMatrix steals bandwidth from.
2. The change you describe was actually made months ago, along with several other major changes to Grid's internal workings. Unless you are a Lua programmer, there is no way to get the previous layout back. This was changed because most people disliked having everything in one row or column.
Also, is there a way to search for text within a thread in this forum? I mean this thread alone is showing as 282 pages... I don't mind searching for my answer, but I'm leery of manually digging through 250+ pages of posts to find it. =/
On the search page you select "show result as [ ] thread [ ] post"
Edit: Actually read the error and it's for gridstatusres. Nvm for this thread :P
Thanks, that has helped me in searching a lot. Though I still haven't been able to find anything in the past hour or so on how to make grid a little less grid and little more rectangles.
Frame > Advanced > Height and Width
First to preface, I use Recount as Load on Demand so it doesn't memory hog in bgs/arena/etc. if I don't care about stats, but do load it for raids. Grid I always have load at log in. (Grid r1174, Recount r1039)
I get this error when I load Recount (w/ libs embedded or w/o) and Grid has frames up on the screen. No error when it's not displaying anything. It doesn't seem to mess anything up that I can tell, but then I do get random black frames on Grid occasionally (until hp is updated from a buff or heal/dmg) and was wondering if this had anything to do with it.
Interface\AddOns\GridFrame.lua:391: Usage: <unnamed>:SetFont("font", fontHeight [, flags])I posted this on Recount's thread as well to see if anyone knows what might be causing this error and thanks for your time if you can come up with anything.
P.S.- Is the black frames every now and then on Grid related to something else or might this be causing that?
This is a likely caused by your Grod settings specifying a font that isn't yet available when Grid initially loads... since you mention Recount, if you're using the font "ABF", that's your problem. ABF is bundled with Recount, but on NTFS systems (most modern Windows systems) addons are loaded alphabetically, so when Grid loads, Recount isn't yet loaded, and ABF hasn't yet been registered with LibSharedMedia-3.0.
Solutions:
While it's possible that the font error causes black frames, it's unlikely. You can easily check though, by setting your font to Friz Quadrata or Arial Narrow (or another font that's guaranteed to be available when Grid loads) and see if you still get black frames. My guess though, is that you either have corruption in your saved variables, or have something "bad" set to use the Health Bar Color indicator, or have a plugin causing problems. Try playing with just Grid and no GridWhatever plugins, and see if the black frames occur. If they don't, it's a plugin problem; post a list of plugins you're using.
In my setup this affects both aguf and grid, and it's a blizz issue. Not sure if it's fixed on the PTR yet.
Andreasg cites this as the issue: http://forums.worldofwarcraft.com/thread.html?topicId=11829374079&postId=118282996524&sid=1#0
Adding Recount to optional dependencies for Grid makes it auto load at startup despite being labeled for LOD, which kind of defeats the purpose of it being LOD. However, doing that did make no errors appear on login.
I run no plugins for Grid, just the bread and butter basic raidframe. It is, however, running unembedded, as are most of my mods. Haven't tested fully if the saved vars deletion will remove the black frames, but setting it up now after deleting the vars and will find out tonight.
Thanks again for your help, and would appreciate any other suggestions for keeping Recount LOD, but not have that error.
Edit: Oh, also of note, I changed Recount's font to FrizQuadrataTT as well and am still getting the error when loading it.
Neither Recount nor Grid are LoD, so I have no idea what you're talking about here... if you've modified either addon from its official version, you're pretty much on your own as far as conflicts between addons go.
Try logging in with only Grid enabled, and changing the font from its current setting to something else that's available when only Grid is enabled. The only choices that should be available there are Arial Narrow, Friz Quadrata TT, Morpheus, and Skurri. Even if it's already set to one of those, change it. Now log out and back in, or reload your UI, and see if the error still occurs. If not, enable Recount too, and see if the error still occurs. If not, enable the rest of your addons, and see if the error still occurs.
If you're using modified versions, try backing those up and downloading copies of the official versions. If this makes the problem go away, then the problem is something you caused, and you should be able to narrow it down from there.
Also, if you're using a modified version of an addon, you should always mention that when posting a bug report. Otherwise, the author (and users who are trying to help) are likely to spend a lot of time looking in the wrong place for a solution to your problem. Reporting that "Line 47 in Version 2.8b gives me this error" is worse than no error message at all when Line 47 in Version 2.8b is actually a blank line, or a line that couldn't possibly generate the error you posted.