After a long long time away from the game, I logged in to the game today and checked on what's happening with Aloft (and other mods) that I wrote a while ago.
Just wanted to say thankyou to acapela for keeping the project alive.
And for the questions above; the WoWInterface download does have mobhealth references, but it doesn't require it, nor does it end up using it since the original Aloft code relating to health 'just works' :)
If my understanding of the secure code is correct, ToT info would only update if you were targeting or mousing over a hostile unit. Not even sure about mouseover. *shrug* It'd probably be easier to do for friendly units.
Thinking about it a little more, I'd kinda like to see ToT info as well. I've got Cowtip set up to show it, but it'd be cool to see on nameplates (especially on my Warrior or Rogue, where most of my attention is on the field and hud, rather than unitframes).
It only works for target and group members.. use the "[TargetName]" tag... if you want it for just the target, try "[IsTarget:TargetName]"
I figured as much and started experimenting with it. It's mostly working already, but I have one or two issues to iron out.
Since it only required a few lines of code change in ManaData.lua, I've committed this and it should be working in r57554. There's a little bar flickering problem that I need to look into sometime, but target mana should basically be working now.
Roartindon, I had assumed that since no changes had been done since October that you were offline, or working on something else now, and since I had seen no problems in the addon with 2.3, it would be ok to update the TOC.. Now I know better.
Sorry, my message wasn't meant to be chastising - apologies if it came across that way. I actually do appreciate it that people bother to update the .toc and other parts of the addons with various improvements. It was meant to be more of an explanation of what went wrong.
So if 2.4 comes along and it works fine, anyone feel free to update the .toc; but please be careful :)
When speedymon decided to update Aloft's .toc to say it was 2.3 compatible, he also inserted some garbage characters in the file - the net result was that CoreModules/CastBarOverlay.lua wasn't being loaded at all, and causing the problems all listed above.
I've committed a fixed .toc file, which should rectify the problem.
Lately (not sure exactly when this started), my Aloft castbars have broken. The appear to start when a spell starts being cast, but then get stuck and never get past about a tenth of the way. The time display for the cast also seems to display the wrong numbers and update oddly. The rest of the Aloft display seems fine. Anyone else seeing this?
I have a theory why this happens...
Aloft's castbars are handled internally by WoW. Aloft doesn't actually update them at all, it just re-styles and re-positions them.
Have you rebooted your computer lately at all?
My theory is that once the computer has been on for a certain amount of time, the timers that WoW uses internally lose precision and cause problems with the internal castbar.
Should be easy enough to prove/debunk.. I've never seen the castbar problems myself unfortunately. :(
I have no idea if this question was asked already or not. Is there a way to make the nameplates clickable to target that mob? I am certian that with the default nameplates you can do that. This would make it infinitly more useful for my play style.
It should already work like that, unless you've disabled it under Aloft->Frame options.