1x Grid-r1438\Statuses\GridStatusName.lua:93: Usage: UnitGUID("unit")
Grid-r1438\Statuses\GridStatusName.lua:93: in function `?'
CallbackHandler-1.0-6:146: in function <...ted\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-6:91: in function `Fire'
AceEvent-3.0-3 (Afflicted):120: in function <...\AddOns\Afflicted\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
That's the expected behavior of the UnitInAnge API, yes. The general purpose of a range check is to show who you can heal; if you're a sheep, you can't cast any heals, so it's reasonably accurate to show everyone as out of range of your heals.
But, as has already been mentioned, if you need multiple-range checking or you prefer the old spell-based API methods, you're free to use the GridStatusMultiRange plugin.
Is this a limitation of the Blizzard UI or something you coded?
As a healer, you need to be thinking ahead of the curve and not reactionary. This change has huge issues if it is not part of a Blizzard limitation.
Yes, if you're a sheep you cannot heal, but you should be able to see who you need to start pumping heals into as soon as the sheep fades.
Is this a limitation of the Blizzard UI or something you coded?
As I already explained, this is how the Blizzard API (not "UI") works. I do not work for Blizzard. I do not develop the Blizzard API, or otherwise have any control over its functionality.
Yes, if you're a sheep you cannot heal, but you should be able to see who you need to start pumping heals into as soon as the sheep fades.
I've been healing since Molten Core, and have no problem with the UnitInRange API. Neither do any of the hundreds of thousands of other people healing with the default unit frames or with other unit frame addons, almost all of which also use UnitInRange. Spell-based range checking was confusing to many users (see the dozens of tickets submitted by users who thought it was broken) and was far more code to maintain.
But, as has already been mentioned, if you need multiple-range checking or you prefer the old spell-based API methods, you're free to use the GridStatusMultiRange plugin.
Grid was written to be extensible through plugins on purpose. If you don't like the core functionality, or don't think the core functionality is enough, there are dozens of plugins you can use to add or change it. If that's not good enough for you, feel free to write your own unit frame addon.
It was working as usual (still showing people in range when I was a sheep/feared etc), but after a fresh install of WoW, when my character is CC'd, the grid range alpha acts as if everyone is out of range. This new change is the confusing part.
That's what changelogs are for. If you don't read them, then you really don't have any room to complain that you're confused when something changes. If you do read them, you'd already know that this change was made.
Any further posts on this subject will be deleted. The change was made, the change was explained (multiple times), and the option to use the old functionality (via the plugin that was specifically released at the same time as the change) was offered (multiple times). There is no point in any further discussion.
Phanx, is there a way to contact you somewhat privately? You turned off your PM's :)
PM me on CurseForge. I don't know why they can't link the forum PM system with the main PM system, but it was annoying getting PMs in two different places on the same site, so I turned off the forum PM system.
I have to apologize first, because I have an issue and not much else to give you to help with figuring out what is causing it. I just updated, curse says it was new as of 10 hours ago. Before this everything was peachy.
As of now the individual bars for health are a flat black with no text or indicators showing up. I go into grid itself, and 'statuses' are empty except for colors. Indicators show nothing, just 'statuses' up at the top and the rest is empty.
I disabled every other addon except for grid, and it is not throwing any errors at me. I am well and truly baffled. Should I just revert to the previous version?
(also, thanks for grid, I absolutely love it. :) )
Blizzard (a) does not show Lua errors by default, and (b) does not show Lua errors that occur early in the loading process even if you enable Lua error display.
Install !BugGrabber and BugSack, and then post the first Grid-related error message that BugSack shows you.
I might be retarded or something. I redownloaded the previous version earlier today so I would have it for raid, logged off for awhile, raided, came back on redownloaded updated grid, and then the addons you mentioned.
Guess what? No issues! I'm assuming I did something wrong/stupid. Oh well, at least I'll have the bug addons if something else goes awry in the future!
+function CompactUnitFrame_UpdateIncomingResurrectIcon(frame)
+ local incomingResurrect = UnitHasIncomingResurrection(frame.unit);
+
+ if ( frame.optionTable.displayIncomingResurrect and incomingResurrect ) then
+ frame.incomingResurrectIcon:Show();
+ else
+ frame.incomingResurrectIcon:Hide();
+ end
+end
+ self:RegisterEvent("INCOMING_RESURRECT_CHANGED");
[/PHP]and a few other snippets that are similiar.
Maybe we can throw away ctra protocl support and show ress-icons ourselfes as a status in grid.
Don't mind the post I did, since is not related to Grid.
I would like though, if anyone can explain to me if hovering over an offline/out of range/dead player is viewed as a valid frame?
Or is that player frame being viewed as simply "world frame"?
I am asking this cause I seem to get an unexpected behaviour where a mouseover macro will not work on those kind of frames.
I would like though, if anyone can explain to me if hovering over an offline/out of range/dead player is viewed as a valid frame?
Or is that player frame being viewed as simply "world frame"?
Frames remain mouse-enabled even if their unit is dead, out of range, or offline. If the cursor is over a dead unit, the "mouseover" unit token points to the dead unit. Likewise for offline or out of range units.
Heya, folks. I've been having an issue with the range fader/transparency for a few weeks now. It suddenly showed up after some server maintenance. I've tinkered around with it as much as I possibly can, but I'm nearing the point where I wanna pull my hair out. I don't want to open up a ticket just yet, as I know the authors have enough to deal with and I'm not sure that this is actually a bug or not.
Whenever I am in a raid and someone dies (but does NOT release), their range fade/transparency shows as if they are within range - even if they are across the zone. When they are ghosts, however, the transparency is correct. I've experienced the same issue with all addons disabled (except for Grid, of course, but including all Grid-related plugins). I've fooled around with all of the death and range settings that I can find, but it's persisting.
My next step would be to delete all of the Grid-related files in my WTF and Addons folder and just start over from scratch. This might make me cry a little since my Grid settings are so specific - BUT!... dealing with this range issue is also making me want to cry :P I figured I'd post a little something here first to see if anyone has any thoughts or suggestions for me. Thanks so much :)
Hey. I have a specific requirement/request, and Im curious if the devs think its remotely possible.
Id like to show shield/absorb-left at the *end of the bar*, as a part of the health bar. That is, when the unit is shielded, the shield should show as a yellow buffer at the end of the green health bar itself. If the unit is damaged, the yellow buffer should appear wherever the end of the green health bar is, eating in to the health-less area.
Does my explanation make sense? Is it likely to be possible? Im a skilled developer, but Ive never worked in Lua before. How much of an undertaking would such a task be?
@elliottcable: The problem I see is how to get the remaining absorb from the API. Doing it "by hand" would require an insane amount of tinkering, but if there's a function or event that gives you this value, it will be possible, and not too hard.
@TWISTEDBULLET: Not sure how Blizzards UI orders the groups, but there are options available. The layouts for Grid are in GridLayoutLayouts.lua. Check out http://www.wowace.com/addons/gridcustomlayouts/ which you can either use or at least look at the options there, they can be used in the layouts file directly.
1x Grid-r1438\Statuses\GridStatusName.lua:93: Usage: UnitGUID("unit")
Grid-r1438\Statuses\GridStatusName.lua:93: in function `?'
CallbackHandler-1.0-6:146: in function <...ted\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-6:91: in function `Fire'
AceEvent-3.0-3 (Afflicted):120: in function <...\AddOns\Afflicted\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
---
http://www.wowace.com/addons/grid/tickets/537-grid-lua-error-in-wow-4-1/
Is this a limitation of the Blizzard UI or something you coded?
As a healer, you need to be thinking ahead of the curve and not reactionary. This change has huge issues if it is not part of a Blizzard limitation.
Yes, if you're a sheep you cannot heal, but you should be able to see who you need to start pumping heals into as soon as the sheep fades.
As I already explained, this is how the Blizzard API (not "UI") works. I do not work for Blizzard. I do not develop the Blizzard API, or otherwise have any control over its functionality.
I've been healing since Molten Core, and have no problem with the UnitInRange API. Neither do any of the hundreds of thousands of other people healing with the default unit frames or with other unit frame addons, almost all of which also use UnitInRange. Spell-based range checking was confusing to many users (see the dozens of tickets submitted by users who thought it was broken) and was far more code to maintain.
Finally, as I've pointed out more than once:
Grid was written to be extensible through plugins on purpose. If you don't like the core functionality, or don't think the core functionality is enough, there are dozens of plugins you can use to add or change it. If that's not good enough for you, feel free to write your own unit frame addon.
I am not trying to argue with you.
It was working as usual (still showing people in range when I was a sheep/feared etc), but after a fresh install of WoW, when my character is CC'd, the grid range alpha acts as if everyone is out of range. This new change is the confusing part.
That's what changelogs are for. If you don't read them, then you really don't have any room to complain that you're confused when something changes. If you do read them, you'd already know that this change was made.
Any further posts on this subject will be deleted. The change was made, the change was explained (multiple times), and the option to use the old functionality (via the plugin that was specifically released at the same time as the change) was offered (multiple times). There is no point in any further discussion.
PM me on CurseForge. I don't know why they can't link the forum PM system with the main PM system, but it was annoying getting PMs in two different places on the same site, so I turned off the forum PM system.
As of now the individual bars for health are a flat black with no text or indicators showing up. I go into grid itself, and 'statuses' are empty except for colors. Indicators show nothing, just 'statuses' up at the top and the rest is empty.
I disabled every other addon except for grid, and it is not throwing any errors at me. I am well and truly baffled. Should I just revert to the previous version?
(also, thanks for grid, I absolutely love it. :) )
Install !BugGrabber and BugSack, and then post the first Grid-related error message that BugSack shows you.
Guess what? No issues! I'm assuming I did something wrong/stupid. Oh well, at least I'll have the bug addons if something else goes awry in the future!
Thanks for the response!
[PHP]
+function CompactUnitFrame_UpdateIncomingResurrectIcon(frame)
+ local incomingResurrect = UnitHasIncomingResurrection(frame.unit);
+
+ if ( frame.optionTable.displayIncomingResurrect and incomingResurrect ) then
+ frame.incomingResurrectIcon:Show();
+ else
+ frame.incomingResurrectIcon:Hide();
+ end
+end
+ self:RegisterEvent("INCOMING_RESURRECT_CHANGED");
[/PHP]and a few other snippets that are similiar.
Maybe we can throw away ctra protocl support and show ress-icons ourselfes as a status in grid.
I would like though, if anyone can explain to me if hovering over an offline/out of range/dead player is viewed as a valid frame?
Or is that player frame being viewed as simply "world frame"?
I am asking this cause I seem to get an unexpected behaviour where a mouseover macro will not work on those kind of frames.
Probably.
Frames remain mouse-enabled even if their unit is dead, out of range, or offline. If the cursor is over a dead unit, the "mouseover" unit token points to the dead unit. Likewise for offline or out of range units.
Whenever I am in a raid and someone dies (but does NOT release), their range fade/transparency shows as if they are within range - even if they are across the zone. When they are ghosts, however, the transparency is correct. I've experienced the same issue with all addons disabled (except for Grid, of course, but including all Grid-related plugins). I've fooled around with all of the death and range settings that I can find, but it's persisting.
My next step would be to delete all of the Grid-related files in my WTF and Addons folder and just start over from scratch. This might make me cry a little since my Grid settings are so specific - BUT!... dealing with this range issue is also making me want to cry :P I figured I'd post a little something here first to see if anyone has any thoughts or suggestions for me. Thanks so much :)
Id like to show shield/absorb-left at the *end of the bar*, as a part of the health bar. That is, when the unit is shielded, the shield should show as a yellow buffer at the end of the green health bar itself. If the unit is damaged, the yellow buffer should appear wherever the end of the green health bar is, eating in to the health-less area.
Does my explanation make sense? Is it likely to be possible? Im a skilled developer, but Ive never worked in Lua before. How much of an undertaking would such a task be?
@TWISTEDBULLET: Not sure how Blizzards UI orders the groups, but there are options available. The layouts for Grid are in GridLayoutLayouts.lua. Check out http://www.wowace.com/addons/gridcustomlayouts/ which you can either use or at least look at the options there, they can be used in the layouts file directly.