|0.1.8c beta||7.87 KB||Mar 12, 2019||8.1.5 +1||284||Download|
|0.1.7b beta||7.87 KB||Dec 14, 2018||8.1.0||97||Download|
|0.1.5b beta||7.72 KB||Aug 11, 2018||8.0.1||155||Download|
|0.1.1b beta||7.28 KB||Aug 9, 2018||8.0.1||42||Download|
|0.1.0b beta||7.28 KB||Aug 8, 2018||8.0.1||36||Download|
|0.0.5b beta||5.12 KB||Jul 28, 2018||8.0.1||67||Download|
|0.0.5b beta||5.12 KB||Jul 27, 2018||8.0.1||26||Download|
|0.0.4b beta||5.13 KB||Jul 26, 2018||8.0.1||27||Download|
|0.0.3b beta||5.05 KB||Jul 25, 2018||8.0.1||32||Download|
|Fade Bars beta||4.97 KB||Jul 25, 2018||8.0.1||17||Download|
|Fade Bars alpha||5.01 KB||Jul 25, 2018||8.0.1||15||Download|
For those who enjoy the stock actionbars and interface of WoW, that also want to have a smooth opacity fade in and out, for a even less obstructed view of the world.
Relies on the default stock actionbars and menu bar frames. Expected to be used without other action bar addons that would replace the default Frames.
/fadebars opens the configuration options.
firstname.lastname@example.org – Email for any major bugs I could work on. Or if you're willing, build off the code yourself.
Due to how the Status Tracking bars in 8.0 (Exp/Rep/Honor/Artifact Power) generate frame names randomly after load. I haven't figured out entirely how to reference them for HookScript. So hovering over them to read isn't ideal while the bottom frames are faded. This is still something I've been researching. Genuinely haven't found really any info on this yet since its still a very new change. (So far looks like its a process that happens in C which can't be modified by user addons. Would have to rebuild the frame.)
Update: Closest I've come to implementing this, is referencing a status tracking bar, and Lua claiming it is a nil value. C error which as far as I've found, means it is an object entirely existing in C and fully protected. Would require me to rebuild the status tracking bars rather than use existing ones. (Might do if I can re-instance the same type of frame)