RangeDisplay
Estimated range display. Type /rangedisplay for configuration or /rangedisplay locked to lock/unlock the frames.
RangeDisplay is a simple range display addon. It is using spell range, item range and interact-distance based checks to determine the approximate range to your current target. Due to the whackyness of interact-distance based checks, recent versions only use those when spell/item based checks are not possible . The display can be configured in many ways (displaying only the max range, adding border and background, etc).
Currently you can set up RangeDisplay to show your current range to your target, focus, pet and mouseover units. The mouseover unit range can be anchored to the mouse or placed at a fixed position.
New in v3.8.0: It is possible to add sound notifications to "range sections" (similar to color setting). The sound will be played when entering the section. If two sections have the same sound file attached to them, then the sound is not played again if switching between the two sections.
This sound notification is enabled by default for the target unit's close range section.
Displaying max range only: if you want to display only the maxRange, you need to set Text to "%d" and tick the Reverse option for the section(s).
Indeed there are many addons that do this for party frames, and do this with a lot less computing (they only need to check the heal range, not all the possible ranges for a more accurate range estimate), so I don't think it's worth implementing it in RangeDisplay.
cheers,
mitch
Thanks, it works perfectly.
Hi,
I've applied your changes and re-packaged range-display. Please try the r211 alpha build, and report back if it works or not.
thanks
mitch
It would be possible, but I think it wouldn't be as useful as you may think (preparing for combat is just as important as actually being in combat as reported by the game). In any case, I stopped playing WoW for a while, so you'd have to wait a bit for this feature :) (or try to find someone on #wowace to implement it for you).
cheers,
mitch
Any way to fix this?
Are all settings lost, or just frame positions?
What other addons are you using?
cheers,
mitch
If I adjust anything after that, regardless of whether I've got frames locked or not, they'll become reset to their default positions.
The only other mods I'm running are AtlasLoot and QuestHelper.
I've just tested the latest download (only loaded RangeDisplay) and I couldn't reproduce your problem. Are you logging back to the same character? By default each character has its own profile, so each one will start from scratch. You can copy settings from another profile from the "Profiles" section in the configuration, if this is the case.
cheers,
mitch
It seems that profiles get reset or deleted also, when I log out or in. Really strange.
Thanks a lot for helping, by the way. : )
Hi,
I've implemented the background thing in v3.1-beta7, check it out. The "ugly" unlocked overlay is still there, just change its alpha to 0 in the code if you really really want to stay unlocked...
cheers, mitch
I get the spell ranges from the blizzard API, so I thought they would be rounded. I'll round them myself in the next release. It's strange though as I can't see how the 28.77777 value came about (cyclone: 20yd, Gale Winds : +2/4yd, Nature's Reach: +10/20%, if all applied, range should be come out as 28.8yd. not 28.77777...)
cheers,
mitch
cheers,
mitch
Been using disembeds for years; yes, used the newest RangeCheck library with that mod. No range problems. Its errors are (unfortunately) frame related, as with many old mods in WoW 3.x.
Ahhh...so unlocking is what causes the increased CPU usage of RangeDisplay. One of the reasons I was such a fan of Simple Range Indicator--besides its superior aesthetic design--was because it used a fraction of the CPU time that RangeDisplay did when I last tested them (with OptionHouse). RangeCheck and all other libraries were disembedded, so it was an accurate comparative test.
I did not lock RangeDisplay during the testing (that I can remember), so that's probably what contributed to the CPU time differences.
Simple Range Indicator's frame was permanently movable, yet it used a lot less CPU than RangeDisplay. So may be worth looking at it to find a better way of handling those OnUpdates.
Anyway, ty for responding :)