eXtreme Unit Buttons 

It's something like this:


heal,NaturesSwiftness,*
heal,HealingTouch,*
heal,Regrowth,*
heal,Rejuvenation,*
heal,Swiftmend,*



solo,player,heal

solo,target,heal

solo,party,heal


There's more but that all works fine.

The NaturesSwiftness will only show up on the player frame and the swiftmend only works on the target frame or have myself/the specific party member targeted.


Thanks for the fix..

Great mod, too bad you stopped development

Anyway.. anyone know how to fix swiftmend and nature's swiftness?

Right now nature's swiftness is only visible on the player frames, while I kinda want it on my party/target frames too.

and swiftmend is only clickable on my target, so I need to target a party member for it to work.

Curious .. what do you mean by the standard cooldown ... because the mod already handles cooldown.

Look at the patches ... for the developers documentation for all your answers and more.

Also, I am working on a new patch to address a button re-refresh problem I observed. One of my good friends continues to play the game and while I was at his place a few days ago to do other things he was in a Kara raid on the second boss and I watched XUB in action. The problem was that the mod regenerated the buttons frequently, so this change is to address this issue.

HOWEVER, I'm not running the game, so debugging is very slow as I have to make the change, email him a copy, ask for feedback, apply change, email another copy, etc. He's trying it out tonight in another raid run. If it works and is beneficial, I'll post v1.7.

Developer documentation is now posted as a patch for the mod. The ZIP file contains a PDF version of the file as well as the original Open Office ODT version. It's not too long at 26 pages. I didn't describe every routine, rather the architecture of the mod. I'll leave up to programmer types to read the code.

I also gathered up 3 postings I made elsewhere on this board and embedded them into the document. This describes the WOW API and LUA links, adding new mod support, and adding movable frames that XUB can take advantage of.

As for v2.0 code, I didn't get much into the code. Most of what I wrote never compiled, and I was contemplating chucking it all and starting again. As well, the more I got into it, the busier I got with work so I really don't know the state of things and decided to not include any code you've requested.

Hopefully I've described enough to get you started. If you decide to take over the mod, I'll write an email to the WoWInterface System Administrators so that you can take control of the posting rather than having to point everybody elsewhere. Let me know what you want to do via a private message.

Regards,
- El

As per your request ...

The original docs, some JPeg's, couple of spreadsheets and a Photoshop PSD file has been uploaded as a patch. I'll try to respond to the rest of your request sometime in the next few days.

- El

For those of you who don't like to mess with editing files, I'll be submitting a TOC update patch before the day is out.

from http://forums.worldofwarcraft.com/th...02909657&sid=1

CPU Profiling
* CPU profiling is disabled by default since it has some overhead. CPU profiling is controlled by the scriptProfile cvar, which persists across sessions, and takes effect after a UI reload.
* When profiling is enabled, you can use the following functions to retrieve CPU usage statistics. Times are in seconds with about-a-microsecond precision:
* NEW - time = GetScriptCPUUsage() - Returns the total timeused by the scripting system
* NEW - UpdateAddOnCPUUsage() - Scan through the profiling data and update the per-addon statistics
* NEW - time = GetAddOnCPUUsage(index or \"name\") - Returns the total time used by the specified AddOn. This returns a cached value calculated by UpdateAddOnCPUUsage().
* NEW - time, count = GetFunctionCPUUsage(function[, includeSubroutines]) - Returns the time used and number of times the specified function was called. If 'includeSubroutines' is true or omitted, the time includes both the time spent in the function and subroutines called by the function. If it is false, then time is only the time actually spent by the code in the function itself.
* NEW - time, count = GetFrameCPUUsage(frame[, includeChildren]) - Returns the time used and number of function calls of any of the frame's script handlers. If 'includeChildren' is true or omitted, the time and call count will include the handlers for all of the frame's children as well.
* NEW - time, count = GetEventCPUUsage(["event"]) - Returns the time used and number of times the specified event has been triggered. If 'event' is omitted, the time and count will be totals across all events.
* NEW - ResetCPUUsage() - Reset all CPU profiling statistics to zero.

GetFunctionCPUUsage, GetFrameCPUUsage and GetEventCPUUsage look very promising.


Drome

PS Have a great long weekend if you get one!

No changes were made to the API code that affect this mod, as of the patch from 05/22/07 (WoW version 2.1). Although unless you enable the load outdated add-ons option, this mod will not function as the TOC files are not updated (unless you choose to manually do so).

The macro coding changes that affect this mod however, aren't many but should be noted as followed.

1) Just as general note for making custom buttons using /cast
- You must now type out the spell name as displayed in game (i.e /cast Flash Heal)

That being said, here are a few macros you can use along with this mod to make casting Power Word: Shield on yourself or your raid/party members with ease, post patch 2.1.

For yourself:
_shieldself,macro,472,/cast [target=player] Power Word: Shield

Then just add the _shieldself custom button to your player group in XUB.

For party/raid members and party pets:
_shieldparty,macro,472,/cast [target=party#] Power Word: Shield
_shieldpartypet,macro,472,/cast [target=partypet#] Power Word: Shield
_shieldraid,macro,472,/cast [target=raid#] Power Word: Shield

Again just add the buttons to the appropriate group in XUB.

A friendly reminder however, as XUB only provides single "/" command macro functions you will not be able to see the spell cooldown or if your intended target is in range or not with the above macros. So although they will allow restore the "one click" Power Word: Shield capability that we have all used to save countless lives, use with caution and know where your allies are.

2) Remember also for macros using /cast [target=UnitID] <spellname> the 2.1 patch now allows multiple arguments to [target=UnitID]. Not really useful for those using XUB, but something to keep in mind for any macros you make for any other action bars.

The present documentation that is included with XUB will still provide all the necessary information for users to get group or self buttons up. Also XUB's formatting of spell names still works for group and self buttons, just not custom buttons (see notes above).

Example XUB Setup for 70 Priest (uses custom macros from above)

Example Player Buttons:
self,InnerFire,*
self,Renew,*
self,FlashHeal,*
self,_shieldself,*
self,AbolishDisease,*
self,DispelMagic,*
self,PrayerofHealing,*

Example Party Buttons:
party,Renew,*
party,FlashHeal,*
party,GreaterHeal,*
party,_shieldparty,*
party,AbolishDisease,*
party,DispelMagic,*
party,BindingHeal,*
party,PrayerofMending,*

Example Party Pet Buttons:
partypet,Renew,*
partypet,FlashHeal,*
partypet,_shieldpartypet,*
partypet,AbolishDisease,*
partypet,DispelMagic,*

Example Raid Buttons:
raid,FlashHeal,*
raid,_shieldraid,*
raid,AbolishDisease,*
raid,DispelMagic,*
raid,PrayerofMending,*

Note: For raid use you may want to use a specific Rank of flash heal to save mana and cut down on overhealing that occurs in raids.

For Example:
raid,FlashHealRank6,*

Now that takes care of the button setup, but they aren't shown yet. Well remember the name of the profile you gave your character when you first ran XUB in game? You used the /xub p <profilename> command to assign one.

Well again according to XUB's documentation, all you need to do now is in the profile window:

<profilename>,<targetframe>,<XUB group name>

So for my examples:
<profilename>,player,self
<profilename>,party,party
<profilename>,partypet,partypet
<profilename>,raid,raid

And remember make sure XUB knows what unit frames you're using. So if you're using XPerl, then change the XUB options setting for the unit frames to XPerl. Also change the option for the appropriate raid frames as well. Otherwise the buttons won't work or show up.

As a final note, I have noticed that when in a raid if members are moved around by the raid leader and groups reorganized, sometimes one or two XUB button sets become non-functional. The only way I've found to restore functionality to all XUB buttons during raids after group reorganization is to use the /console reloadui command.

It would be nice to get a developers section up to segregate the development discussions from the end user stuff (everyone should have access if they desire). Does WoWinterface support that or would a developer site be better. I saw an addon that was up on googles developer site - looked nice for the 30 seconds i gave it.

I am hoping that the new profiler tools can help address the performance issues. I am realinterested if it is the Button Update, buff tracking or something else. I can see modulerizing a couple of the larger functions so the profiling is easier - they mention microsecond accuracy in function calls.

Drome