Grid 

I logged in and checked the GridRange on the debug mode and then pasted "/script GridRange:ScanSpellbook()" in the chat box and nothing happened. I logged in and out a couple times with the same result.

Edit: After turning off my error hide addons I recieved this error

http://www.maj-ace.com/files/griderror.jpg

when I typed in

/script GridRange:ScanSpellbook()

If you could contact me on AIM (Majace1) Xfire(acetbrooks) or even Vent this would be easier on both of us. The others in my guild that use the add-on are having the same problem.

Thanks in advance!

The range checking code hasn't changed, except to exclude pet heals. Feel free to turn on debugging for GridRange and then run /script GridRange:ScanSpellbook() to see what spell it's using for the 40yd check (it'll be the last one listed).

Hello,

Lets me first say, Grid is my crutch as a healer in PVP. It's an amazing add-on.

I customized my version a bit as you can see here.
http://www.maj-ace.com/files/gridtest1.jpg

Unfortunately with the release of 2.0.3 I'm having issues with the range detection of the add-on.

The problem I'm having is:


The range detection, which use to be 40 (and great for PVP healing) appears to be much shorter now.

I'm using the newest version of the add-on which I downloaded here. I also spent a ton of time searching for a solution before I created this post.

Is there any way I can change the range back to 40 for healing?

Thanks in advance,
Maj

The versions at wowace are development versions and may or may not work. If you're using the development versions from wowace, you should report problems on the wowace forums.

If you want tested versions of Grid, download from here. I'll be releasing another tested version before TBC.

The SecureTemplates.lua line 816 error is a harmless bug in Blizzard's code. Just ignore it until they fix it (hopefully in the next patch).

Grid r23489
WoW v2.0.1.6180
Joined a raid.
Error appears when joining a raid initially, afterwards I cannot detect anything wrong with Grid.

Date: 2007-01-06 15:55:21
ID: 51
Error occured in: Global
Count: 1
Message: ..\FrameXML\SecureTemplates.lua line 816:
table index is nil
Debug:
[C]: ?
..\FrameXML\SecureTemplates.lua:816: SecureRaidGroupHeader_Update()
[string "GridLayoutHeader1:OnShow"]:2:
[string "GridLayoutHeader1:OnShow"]:1
[C]: Show()
Grid\GridLayout.lua:830: CheckVisibility()
Grid\GridLayout.lua:768: UpdateDisplay()
Grid\GridLayout.lua:763: LoadLayout()
Grid\GridLayout.lua:698: ReloadLayout()
Grid\GridLayout.lua:551:
Grid\GridLayout.lua:545
[C]: ?
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:320: TriggerEvent()
Grid\GridCore.lua:319:
Grid\GridCore.lua:295
[C]: ?
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:320: TriggerEvent()
oRA2\Libs\Roster-2.1\Roster-2.1.lua:194: ?()
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:757:
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:751
[C]: ?
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:427:
...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:403
AddOns:
Atlas, vv1.8.6b5
AtlasBattlegrounds, vv1.8.6b5
AtlasDungeonLocs, vv1.8.6b5
AtlasFlightPaths, vv1.8.6b5
AtlasLoot, vAtlasLoot Enhanced v2.01.00
AtlasOutdoorRaids, vv1.8.6b5
BGAlerts, v1.1
BGSoundAlerts, v2.0
BigWigs, v2.0 r23774
Bongos, v6.12.14
BongosActionBar, v6.12.5
BongosMapBar
Cartographer, vr29514
CartographerMining, v1.0
ClearFont2, v2.0
Clique
CTCore, v2.0 (CTMod 2.0)
CTExpenseHistory, v1.5 (CTMod 2.0)
CTMailMod, v1.5 (CTMod 2.0)
CTProfiles, v1.2
DefaultChatTab, v1.1
FlightMap, v2.0-1
eCastingBar
FishingBuddy, v0.9 Beta 6
GFWAdSpace, v2.0.2
GFWGemologist, v2.0.3
GFWGuildentipper, v2.0
GFWReagentCost, v2.0.1
FuBarBagFu, v2.0
FuBarClockFu, v2.0
FuBarDurabilityFu, v2.0
FuBarFuXPFu, v3
FuBarHonorFu, v2.0
FuBarLocationFu, v2.0
FuBarMoneyFu, v20000-1
FuBarPerformanceFu, v2.0
FuBarVolumeFu, v2.0.$Revision: 20572 $
FuBar, v21575
Grid, v23489
HealPoints, v2.0
KLHThreatMeter, v18.11
LootLink, v783
LootLinkAutoLinkBot, v1.0.0
LootLinkQuickChatlink, v1.2.0
LootLinkQuickSearch, v1.2.0
MetaHud, vv20000-2
MobInfo2, v3.14
CEnemyCastBar
CECBDebuffs
CECBPvPModule
OmniCC, v6.12.05
oRA2, v2.0.$Revision: 20657 $
Outfitter
PallyPower, v2.00.48
PerlArcaneBar
PerlCombatDisplay
PerlConfig
PerlFocus
PerlParty
PerlPlayer
PerlPlayerPet
PerlTarget
PerlTargetTarget
CharacterProfiler, v2.0.1
sct, v5.3
sctd, v2.2
SimpleCombatLog, v1.0.20737
SSAutoTurnIn
SSBGLibrary
SSBGReformat
SSLoader
SSOverlay
SSPVP
Stubby, v1285
SuperInspect, v2.0-beta-9
SuperInspectUI
Swatter, v3.9.0.1301
vBagnon, v6.12.12
vBagnonForever, v6.12.4
Yatlas, v0.7.5

http://img219.imageshack.us/img219/559/clickzj1.jpg

Image with the output of the frame debug thing when the bug is active.

Ok, I don´t know that. I just wanted to be up-to-date and I was wondering if your version from December was really the newest. So just to understand it in the right way: I only have to download from here and not from wowace.com? What persons update these files at wowace? I thought you did it...Thanks a lot I will test this version.

See above:

Version r23489 get an error:

GridFrame.lua:354 attempt to call method 'utf8sub' (a nil value)

German client.

No frames are shown.

I will do that next time it happens - something which I realized yesterday though is that it was fine for several AV's and the bug didn't pop up once - however, when I was in AB, and then left halfway through to join AV, the bug popped up straight away. Also, when I tried again last night, I was in a group with a friend before I joined the AV battleground and the bug popped up straight away.

I'll try again when I get home so I can test, it could be a coincidence but it seems as if the bug appears if I'm already in a group then join a battleground without leaving it first (as is the way in battlegrounds, where you're in two raids at once practically, can still talk to people in your party/raid who aren't even in the battleground while communicating with the battleground raid via bg.) Or if you accept to join a second battleground without first leaving the initial battleground you're in.

Here's a sneak peek at the next release. I'll be testing it for the next week in order to have it ready before the 16th.

Changes:
- Remove center text 2 indicator from the menu if it's disabled.
- Layout now reloads when switching between solo/party/raid/battleground. This should fix raid groups not showing up occasionally.
- Made range module more friendly to addon developers.
- Added UTF-8 support. GridFrame counts characters properly when truncating names now.
- Increased maximum text length to 20.
- Health updates should be more responsive.
- Use the right addon communication channel in battlegrounds.
- Improved group placement, groups shouldn't end up stacked ontop of each other anymore.
- Updated to Roster-2.1 and Banzai-1.1. This will break any Grid addons that depended on Roster-2.0 and Banzai-1.0! It also improves performance, so it's worth it.

There's an open ticket for this issue http://www.wowace.com/trac/ticket/97

I need a way to reliably reproduce the bug, unfortunately it seems to be random. Reloading the UI usually fixes it, but I'd much rather it not happen in the first place.

The next time this happens to you, turn on debugging for the GridFrame module and then run /script GridFrame:ListRegisteredFrames() and check your combat log (or whatever ChatFrame2 is for you). The output will help me figure out what's causing this problem.

First off - love these raidframes, the best I've ever used for healing by far.

I have an issue though. It seems that quite often a spot in the raidframes becomes 'dead', as in clicking on whoever's in that spot at the time doesn't target them. The spot varies, it's usually near the last group.

As an example this is from an AB from earlier: http://img320.imageshack.us/img320/5...ickablefq0.jpg. Apologies for the poor quality, MSPaint In the image every single person is clickable except the person at the end of the second group (in this case Mot..) I've tried playing around with grid's config a lot to try to fix it, and I've also tried using old versions, and the current beta (from WoWAce) before reverting back to the 19919 build as I had the issue with all of them.

I get no errors or anything when clicking on the target. Just nothing happens, although mousing over the target does display the tooltip. Any ideas?

And as per the requested info thing: I'm using grid r19919 atm. I've tried 18940, and 22790 (from WoWAce) both of which I had the same problem with, and I'm using WoWEU current version (2.0.1 iirc.)

This is interesting. When I look at my addons page at the character screen, each mod that uses ACE have "Ace2" after the name. With out exception, all the mods but MrPlow the letters are of a different color than Grid's "Ace2".

Being that Grid is working fine otherwise I think I can wait for the next update of Grid. Thanks again for the great mod.

It sounds like a problem with the version of AceConsole that your other Ace2 addons are using. You can either wait for the next Grid release, or see if there's a newer version of any of your other Ace2 addons in order to get an updated version of AceConsole.