Given how Auracle configuration works, I think we are speaking of a dozen lines that would reuse the same code as the "worthy" defaults do. That is not bloating like, by example, adding cooldown support could be.
I looked into this briefly awhile back, and I wasn't sure I could reliably maintain the identity of "mouseover" without having to poll for it constantly. I'll look into it again, but my fear is it would either be slow or potentially inaccurate.
IIRC, there is a UPDATE_MOUSEOVER_UNIT event. Dunno if it is fired often enough though.
After further testing, I like very much the concept of AuraHUD. However the configuration is very tedious. I cannot wait for configuration inheritance/copy you were talking about.
BTW, could you add the "mouseover" unit in the list of possible window units ? It could be very handy for druids and warlocks to check their HoTs/DoTs. Actually I use mainly [target=mouseover] macros with my druids, having a way to clearly see HoTs of my target would be wonderful.
Adirelle and Elsia: Currently, every alpha setting is independent. The window border and background have alpha in their color controls, and the background alpha doesn't affect any trackers. But trackers also have border and tint colors which include alpha, so tracker opacity is set that way. I'm considering making the alpha settings separate from colors, so then the window's alpha could be made to affect its trackers. But I think once settings are easier to change/propagate globally, it'll be easier to just change all the trackers' tint alpha to get the same effect.
IIRC, alpha set using :SetAlpha is combined with alpha of children frames (as scaling does), so you could have a window alpha setting that would not mess with border/backdrop/tracker settings while still visually applies to the window.
BTW, I'd like a "hide tracker if missing". I sometimes just want to know if an aura is here but do not care if it is not. By example, I made an "invulnerability" tracker that shows iceblock, divine shield or cloak of shadows on hostile pvp players. ATM, if I wanted to hide it when the target actually did not have it, I had to separately set icon and border alpha to 0.0. (And I didn't even checked if it catched mouse events, which I hope it would not.)
This is planned. Specifically, there will be global defaults for both windows and trackers; when a new window is created, it will get a copy of the global window settings for itself, and a copy of the global tracker settings as that window's own tracker default settings. When a new tracker is created, it will get a copy of it's window's tracker settings. It will also be possible to propagate any of these settings back down to existing windows/trackers on a per-setting basis.
Does it mean I can easily update the global config and that all non-custom tracker settings will automagically get updated accordingly ? Or will I have to copy the new global settings into each tracker ?
A big bug: AuraHUD does not detect when an aura is applied on the unit. For the target unit, I can force an aura detection by dropping my target and selecting it again (e.g. trigger a PLAYER_TARGET_CHANGED event) but there is no way to do so with player or pet.
About the tracker display settings (colors, size, scale, and the like): I think you should consider implementing two-level settings: 1) global, common settings and 2) the possibility to override them on a per-tracker basis (using a checkbox). Actually I can imagine the pain of changing your mind about the border color when you have 5 or 6 trackers configured...