eXtreme Unit Buttons v1.9 Release Candidate 8 : WoWInterface Downloads : Plug-Ins & Patches

		WoWInterface Downloads » Plug-Ins & Patches
eXtreme Unit Buttons v1.9 Release Candidate 8

Category: Plug-Ins & Patches

Addon Information

This file is a Addon for eXtreme Unit Buttons by paladindrome. You must have that installed before this Addon will work.

Author:	paladindrome [more]
Version:	1.9RC8
Date:	01-31-2009 05:33 PM
Size:	86.87 Kb
Downloads:	267
Favorites:	1
MD5:

Pictures

eXtreme Unit Buttons v1.9 Release Candidate 8

Change Notes for 1.9 rc8:
---------------------------

Bug Fixes from Wowinterface:

Friendly buttons on Hostile and Hostile button on Friendly would show during the Global Cool Down.

I reordered the code back to closer to what is was in Rc6 and
this problem has gone away. The code progression is now different
from what Tay had so we need to test to verify it hasnt
caused other issues.

Strata chages to Frame causeing issues.

Added two constants with RC6 values and update the setting code.

A Use for Debuff (! in extra) was not working.
Changed use debuff code to work

Comments - eXtreme Unit Buttons v1.9 Release Candidate 8

Comment Options

Page 1 of 4

Last »

04-20-2009, 02:04 AM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Re: Re: Re: Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by paladindrome
Uploading now - sorry - thanksfully the kids are still goofing around and I remembered that i forgot (???)

I am guessing that Blizz made some change in how they manage raid parties - this was very OLD code.

Drome

Just downloaded it, and will give it whirl.

Any bug reports/comments, I'll post in the comments section for that build (http://www.wowinterface.com/download....html#comments).

04-19-2009, 09:15 AM

paladindrome

A Kobold Labourer

Forum posts: 0

File comments: 149

Uploads: 4

Re: Re: Re: Re: Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by Cosmic Cleric

EDIT: I just checked, and didn't see a new version in the "Optional Files" section

Uploading now - sorry - thanksfully the kids are still goofing around and I remembered that i forgot (???)

I am guessing that Blizz made some change in how they manage raid parties - this was very OLD code.

Drome

Last edited by paladindrome : 04-19-2009 at 09:23 AM.

04-18-2009, 05:18 PM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Re: Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by paladindrome
Zoning shouldn't cause XUB any issues - we have already created the buttuns and the normal update cycle will show or not show them. Adding users and moving people around does cause us a cascade of work. This is what I would like to work on for the next release.

For this problem I have gotten one step closer - Blizzard Raid frames are different from all of the other raid frames in that XUB will associate multiple frames per unit:

Code:

if ( XUB_RaidTable[testFrameUnit] ~= nil ) then XUB_RaidTable[testFrameUnit] = XUB_RaidTable[testFrameUnit] .. "/" .. testName; else

This is what caused the aFrameNo: (2) error message in the screen shot. I do not know why this would be activated - the only conjecture I have is that a user was moved during the middle of our update and this caused us to see that player as having two unit frames.

When we get into the button creation process we check to see if there are more then 1 frame and if so we post the error (Why associate multiples in the first place then?). The joys of working on old code with three different authors. I think the most straightforward approach is to comment out the way the Blizzard frames are coded so they act the same as the add on raid frames and get this version out as a beta/alpha.

I am on vacation starting tomorrow so I will put it out today - but wont be able to help for a bit.

Drome

First off, thank you for your help, appreciate it.

Second, while I don't KNOW if I was moved around, I do remember, when first joining the raid, I wasn't in the last position, but at the time the error happened, I was. Coincidence or the cause, your guess is as good as mine. /shrug

Third, I'll try out the new code (haven't checked yet, but based on your comments I'm assuming you've uploaded it already?) and see how it affects the problem, and report back.

Fourth, enjoy your vacation!

EDIT: I just checked, and didn't see a new version in the "Optional Files" section (http://www.wowinterface.com/download....html#optional). I guess you didn't get a chance to upload it before going on vacation? I also checked the old Google dev areas too (http://groups.google.com/group/develop_xub/files)(http://code.google.com/p/extremeunit...downloads/list).

UPDATE! I was in a Naxx raid, nobody zoning in/out, but the raid leader started rearanging people already in the raid into different groups! As soon as this happened, the same error came up again. So it has to do with moving people around.

UPDATE 2: Same raid, someone left, same error happened. No position switching.

Last edited by Cosmic Cleric : 04-18-2009 at 10:26 PM.

04-18-2009, 09:12 AM

paladindrome

A Kobold Labourer

Forum posts: 0

File comments: 149

Uploads: 4

Re: Re: Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by Cosmic Cleric
I was inside the instance already with many members, and other members were zoning in. I can't say if members were being moved around, as I was not the leader, and things were kind of hectic (as usual when a PUG is getting its act together).

I can definately say though that people were zoning in at the time.

Zoning shouldn't cause XUB any issues - we have already created the buttuns and the normal update cycle will show or not show them. Adding users and moving people around does cause us a cascade of work. This is what I would like to work on for the next release.

For this problem I have gotten one step closer - Blizzard Raid frames are different from all of the other raid frames in that XUB will associate multiple frames per unit:

Code:

if ( XUB_RaidTable[testFrameUnit] ~= nil ) then
          XUB_RaidTable[testFrameUnit] = XUB_RaidTable[testFrameUnit] .. "/" .. testName;
else

This is what caused the aFrameNo: (2) error message in the screen shot. I do not know why this would be activated - the only conjecture I have is that a user was moved during the middle of our update and this caused us to see that player as having two unit frames.

When we get into the button creation process we check to see if there are more then 1 frame and if so we post the error (Why associate multiples in the first place then?). The joys of working on old code with three different authors. I think the most straightforward approach is to comment out the way the Blizzard frames are coded so they act the same as the add on raid frames and get this version out as a beta/alpha.

I am on vacation starting tomorrow so I will put it out today - but wont be able to help for a bit.

Drome

04-17-2009, 02:27 PM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by paladindrome
Were members being moved around groups when the issue happened?

It seems to have the most issues with the changing of party/raid members. The basic approach is - Hey there is a change let me reset everything. I would like to get a relase out for 3.1 and look at a rewrite of the button creation to minimize the work that is done while in raid.

I looked at the changes between RC7 and RC8 and I didnt see anything that should impact the button creation. The specifc error of aFrameNo ~= 1 (not equal) is actually quite confusing - the code specifcally looks to see if there are multiple frames (aFrameNo = 2 in your screenshot). I am not sure how this would occur.

A head knocker for sure.

Drome

I was inside the instance already with many members, and other members were zoning in. I can't say if members were being moved around, as I was not the leader, and things were kind of hectic (as usual when a PUG is getting its act together).

I can definately say though that people were zoning in at the time.

04-16-2009, 06:23 PM

paladindrome

A Kobold Labourer

Forum posts: 0

File comments: 149

Uploads: 4

Re: Re: Re: Bug Report while in a Raid

Quote:

Originally posted by Cosmic Cleric
Yes, this is with the latest downloadable versio, RC8.

Sorry to add to the woes. For what its worth, XUB doesn't seem to be in a healthy condition when used in a raid.

Were members being moved around groups when the issue happened?

It seems to have the most issues with the changing of party/raid members. The basic approach is - Hey there is a change let me reset everything. I would like to get a relase out for 3.1 and look at a rewrite of the button creation to minimize the work that is done while in raid.

I looked at the changes between RC7 and RC8 and I didnt see anything that should impact the button creation. The specifc error of aFrameNo ~= 1 (not equal) is actually quite confusing - the code specifcally looks to see if there are multiple frames (aFrameNo = 2 in your screenshot). I am not sure how this would occur.

A head knocker for sure.

Drome

04-14-2009, 10:27 PM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Bug Report while in a Raid

Quote:

Originally posted by paladindrome
And some of the buttons double up. This is with RC8?

I assume the prob is aFrameNo~=1 as aUnit looks liek it is raid22.

Sigh . . .

Drome

Yes, this is with the latest downloadable versio, RC8.

Sorry to add to the woes. For what its worth, XUB doesn't seem to be in a healthy condition when used in a raid.

Last edited by Cosmic Cleric : 04-15-2009 at 09:58 PM.

04-14-2009, 08:17 PM

paladindrome

A Kobold Labourer

Forum posts: 0

File comments: 149

Uploads: 4

Re: Bug Report while in a Raid

Quote:

Originally posted by Cosmic Cleric
Got a "We are here because aUnit is NOK or aFrameNo~=1" message.

aUnit: (raid22)

...

FYI, please note in the screenpics the the bars to the right of each character is higher up than it should be.

And some of the buttons double up. This is with RC8?

I assume the prob is aFrameNo~=1 as aUnit looks liek it is raid22.

Sigh . . .

Drome

04-10-2009, 01:11 AM
Cosmic Cleric A Murloc Raider Forum posts: 8 File comments: 269 Uploads: 8	Bug Report while in a Raid Got a "We are here because aUnit is NOK or aFrameNo~=1" message. I have a screenpic to show the problem, but basically it was the following info... We are here because aUnit is NOK or aFrameNo~=1. XUB-Error: aUnit is NOK or aFrameNo~=1. aFrame: (RaidPullout5Button4) aUnit: (raid22) aDestinationUnit: (raid22) aSpellName: (Dispell Magic) aRank: () aThreshold: (0) aExtra: (Magic) aToolTip: ( Starts blinking when unit has these debuffs: Magic) aExcludeUnits: () aWidth: (25) This happened while in a 25 man Vault run, and I was inside the zone and people were zoning in. I actually had two disconnects while inside Vault too so whatever XUB is freaking out about is bad enough to potentially destabilize the client. Using ag_UnitFrames as my UI (ag_UnitFrames-r685.zip). I was in the last raid position in the last group, and the error happened with my character. This may be significant, as in the past, I've been in the same instance and have not had disconnects and/or XUB errors. Maybe its an array index out of bounds problem? Here are the screenpics showing my UI at the time of the error... http://img2.imageshack.us/img2/7712/...0809201653.jpg http://img2.imageshack.us/img2/9869/...0809201700.jpg http://img2.imageshack.us/img2/6076/...0809201706.jpg FYI, please note in the screenpics the the bars to the right of each character is higher up than it should be. Whenever someone enters/leaves the raid, this happens, and I have to type a "xub /p" to get them to line up to the right of the right character name. Not sure if this is related to the problem or a completely different problem, but as I said, a "xub /p" fixes that problem right away. Last edited by Cosmic Cleric : 04-10-2009 at 01:15 AM.

04-10-2009, 01:11 AM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Re: Re: Re: Re: Re: Problems in raids

Quote:

Originally posted by Cosmic Cleric
Would I have to actually create the 'c' profile to get this trick to work? Will XUB work if I supply a profile name that doesn't exist?

Originally posted by tayedaen
As I wrote, the profile 'c' does not need to exist.

Apologies, didn't notice the "/XUB p <some_not_existing_profile>" statement earlier in your same post.

Last edited by Cosmic Cleric : 04-10-2009 at 01:12 AM.

04-09-2009, 12:35 PM

tayedaen

A Murloc Raider

Forum posts: 4

File comments: 169

Uploads: 36

Re: Re: Re: Re: Re: Re: Problems in raids

Quote:

Originally posted by Cosmic Cleric
Would I have to actually create the 'c' profile to get this trick to work? Will XUB work if I supply a profile name that doesn't exist?

As I wrote, the profile 'c' does not need to exist.

04-07-2009, 12:23 AM

Cosmic Cleric

A Murloc Raider

Forum posts: 8

File comments: 269

Uploads: 8

Re: Re: Re: Re: Re: Problems in raids

Quote:

Originally posted by tayedaen
Instead of /console reloadui you could use this (because it's faster):
/XUB p <some_not_existing_profile>
/XUB p <your normal profile>

Lets say your normal profile is called 'normal'.
Then in thsi example you could write:
/XUB p c
/XUB p normal

I know this is only a workaround, but I have no time for XUB at the moment.

cu
tay

Would I have to actually create the 'c' profile to get this trick to work? Will XUB work if I supply a profile name that doesn't exist?

04-06-2009, 11:31 AM

tayedaen

A Murloc Raider

Forum posts: 4

File comments: 169

Uploads: 36

Re: Re: Re: Re: Problems in raids

Quote:

Originally posted by Cosmic Cleric
Interesting enough, xub /p doesn't fix the problem. It takes a /console reloadui to fix it. Tried multiple times over multiple days, xub /p doesn't work to clear the unneeded buttons. /shrug

Instead of /console reloadui you could use this (because it's faster):
/XUB p <some_not_existing_profile>
/XUB p <your normal profile>

Lets say your normal profile is called 'normal'.
Then in thsi example you could write:
/XUB p c
/XUB p normal

I know this is only a workaround, but I have no time for XUB at the moment.

cu
tay

03-25-2009, 05:04 PM

paladindrome

A Kobold Labourer

Forum posts: 0

File comments: 149

Uploads: 4

Quote:

Originally posted by Pester I realize that this may seem quite trivial, but how do you get to enter text into the group box?

Sadly it is a very good question.

You have to find - just - the right spot. Once you get one line in it it is very easy but the first line can be frustrating. Try clicking where the left most part of a t would be.

Quote:

and should the top box already be populated?.. just curious

The top box is entirely optional.

The basic config is:

Enter on spell in lower left box: heal,HolyLight,*
Enter one line in lower right box: normal,party,heal

Verify and Save

Configure you unit frames (default is blizzard standard)

enter the command: /xub p normal

Drome

03-25-2009, 02:45 AM
Pester A Cyclonian Forum posts: 49 File comments: 17 Uploads: 0	I realize that this may seem quite trivial, but how? do you get to enter text into the group box?.. I am only able to enter information into the Profiles box... I am using the latest release and no other add-ons are loaded. I Make a group with one spell "heal,HolyLight,*" copy it, but there is no way to paste it into the group box, only the profile.. and should the top box already be populated?.. just curious THanks!

Page 1 of 4

Last »

Report this File

Category Jump: