-
  #### **Grid version:**
  Check the addon’s TOC file if you’re not sure!
  Grid-r1525
----------------------------------------
  lvl 85 BElf HPala

  #### **Description of the problem:**
- From the 1st version of Grid for 5.0.4 patch, updates on people who join the group are really slow. They'll either appear after half a minute or require a change on the layout or /reload ui. I'm in DS for example, someone gets invited and i'm able to see him after he enters the instance. Anyone noticed any dealy like this?
+ From the 1st version of Grid for 5.0.4 patch, updates on people who join the group are really slow. They'll either appear after half a minute or require a change on the layout or /reload ui. I'm in DS for example, someone gets invited and i'm able to see him after he enters the instance. Anyone noticed any delay like this?
  Also whenever im switching Beacon of Light to another target, old BoL still is shown for a few seconds.(didnt check this with only grid active tbh, but i thought i should mention that)
  #### **Steps to reproduce the problem:**

You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #28

  Phanx Nov 25, 2012 at 04:01 UTC - 0 likes

  Okay, marking this as fixed. If the issue is not fixed for you, please post a comment on this ticket instead of opening a new ticket.

• 

  • Reply
  • #27

  bent42 Nov 21, 2012 at 05:17 UTC - 0 likes

  I haven't tested it thoroughly but it seems to be fixed! Thank you! That bug was driving me nuts!

• 

  • Reply
  • #26

  Phanx Nov 11, 2012 at 02:57 UTC - 1 like

  Interesting.

  That line was added back when title-swapping addons were really popular, and people would change their character's title every few seconds, thus causing massive framerate drops for everyone else in their raid. Ignoring the name change event "solved" the problem.

  Blizzard has since made changing your title a protected action, so addons can't automate it, and that line is probably not needed anymore.

  I'll go ahead and remove that line, and push out a new release in a few days if nobody reports any issues with the alpha.

  Thanks for looking into this issue and (hopefully) finding the solution. I've been really busy at work lately and haven't had time to do any testing on this.

• 

  • Reply
  • #25

  warbaby Nov 11, 2012 at 02:02 UTC - 1 like

  Finally, I'v found out the point.

  in GridLayout.lua, function GridLayout.prototype:Reset()

  self:UnregisterEvent("UNIT_NAME_UPDATE")
  

  Remove this line and everything seems ok. But there must be reasons for that line, anyone knows?

• 

  • Reply
  • #24

  warbaby Nov 09, 2012 at 04:59 UTC - 1 like

  hi guys I've looked through the SecureGroupHeaders.lua and find some ways to test the Blizzard code result. And I found out that when SecureGroupHeader_Update is called after "GROUP_ROSTER_UPDATE", the GetGroupRosterInfo("RAID", 40) return nil if the 40th raider has just joined the battleground (the number 40 is just an example).

  That's the source of this problem.

  And I've seen an article before, http://www.wowpedia.org/Patch_5.0.1/API_changes. It says "requesting the GUID of another party member (possibly raid too - not tested) while responding to the new GROUP_ROSTER_UPDATE event during initial UI load while you are already in a group returns nil. This was not previously the case with the old PARTY_MEMBERS_CHANGED and RAID_ROSTER_UPDATE events."

  I think that the problem with GetGroupRosterInfo is just the same.

  If there would be a workaround, I think we can compare the number of shown UnitButtons and GetNumGroupMembers() which is always correct, and perform a GridLayout:ReloadLayout() when neccessary and when out of combat.

  Last edited Nov 09, 2012 by warbaby
• 

  • Reply
  • #23

  Clarx Oct 31, 2012 at 20:45 UTC - 0 likes

  Having the same issue, that it takes up to 1 minute before Grid shows everyone after I got invited, yet today I noticed something new. Sha-raid formed, 4 spots left (all empty spots in group 8), and i got my Blizzard raid-pannel (hit 'O' > raid-tab) opened up. I see the message "Player 'Z9' joins the raid, yet he didnt appear in the Blizz-pannel for 5-10 sec. and not in Grid for further 10 sec.

  Last edited Oct 31, 2012 by Clarx
• 

  • Reply
  • #22

  Phanx Oct 26, 2012 at 21:51 UTC - 0 likes

  xentaros:
  I think this is a Blizzard bug...

  That was my thought as well, especially since one of the previous commenters mentioned that GridRoster is silent when the bug occurs, but I didn't have time to do any debugging last night to verify that or try to find a workaround. If it only happens in battlegrounds, I guess I can add a workaround to listen for the "X joined/left the battleground" messages and force an update, though that seems like a pretty clumsy hack.

  Once I have time to test and debug (assuming I can reproduce the problem; it happened in Eye of the Storm, but hasn't happened in any other BGs I've entered to test since this ticket was submitted, or in any PVE content I've done) if I can confirm that it is a bug with the client not firing the proper events, I'll post a report on the Blizzard bug forums as well.

• 

  • Reply
  • #21

  xentaros Oct 26, 2012 at 13:41 UTC - 0 likes

  For people with this problem, I've been using this macro as a workaround when it happens (out of combat only): /run LibStub("AceAddon-3.0"):GetAddon("Grid"):GetModule("GridLayout"):Reset()

• 

  • Reply
  • #20

  xentaros Oct 26, 2012 at 13:28 UTC - 0 likes

  I think this is a Blizzard bug because if you open the raid frame while players join a BG, you will see that grid and the blizz raid frame are always in sync with each other. However, they will sometimes both fail to show new members who have entered the raid. Closing the blizz raid frame and reopening it causes it to update and properly reflect the players (but grid will still be wrong). I suspect events are not being fired properly by the wow client.

  Here is a screenshot of a rogue who is not shown in either window. It was like this for 30+ seconds:

  Last edited Oct 26, 2012 by xentaros
• 

  • Reply
  • #19

  Phanx Oct 26, 2012 at 12:46 UTC - 0 likes

  Probably not, but I did actually see the bug happen today, so there may be some hope yet.