We often get clues about the issue by looking at your entire UI, so please take some screenshots and add them here.
#New elvui update target frames 2019 update
Now uses Class Mode by default and a fixed 0.7 UIScale - NameplateCooldowns and Diminish Profile update v2.14 - Misc. v2.15 - Misc changes and update for ElvUI 11+ and the new Nameplates settings. When it did it was the blizzard one on the top left of the screen.ĭo you have any other information which might help us track down the issue?: More Nameplates settings in the installer, to keep up with the new additions in ElvUI 11.07. Installation: Before installing this UI please go to /ec -> profiles and create a new profile. New classic update no longer shows the target frame. Adding different frame styles, interchangeable actionsbars, new textures and fonts. Describe the exact steps we need to take in order to reproduce the issue.: Please explain the issue you're having with as much detail as possible. If you received an error then post it below (use the 'code' bbcode): Did you get an error or do you still experience the issue?: Do you still experience the issue?:Ĭheck for lua errors by using the command "/luaerror on" without quotes. Do you still experience the issue now?:ĭisable all addons and use the default UI to make sure it is not an issue with the WoW client itself. Version of ElvUI (use /estatus command ingame to check):ĭisable all addons except the two called "ElvUI" and "ElvUI OptionsUI". After I disabled it and re-enabled it, it no longer shows up. When it did it was the blizzard one on the top left of the screen. Maybe that's enough to make the target frames behave properly when party members are added while in combat.New classic update no longer shows the target frame. Maybe as easy as calling ":Hide()" on all pre-built party target frames at login (if setting is off) and at setting-disable, or ":Show()" at login/setting-enable. Right now it seems like all default to "visible by default".
#New elvui update target frames 2019 code
Perhaps only doing the correction once per party member and then never again for that game session?Īlternatively, perhaps much better (if possible): Change the code so that if the player toggles "Enable party targets" on/off, or when they login (with it on/off), pre-configure all party target frames as "visible by default" or "hidden by default". Maybe by doing target frame visibility correction in the PLAYER_REGEN_ENABLED (combat ending) event, in some CPU-efficient way. If that's true, then it's impossible to hide/show secure So if this report is correct (that party targets appear if we are in combat while someone joins our party or while we join a party), then what's probably needed is something to check for combat and then hide it later, after combat, instead. The API for checking if a secure frame can be hidden/shown/change attributes is InCombatLockdown(). "Player joined party we don't want targets? hide their target frame" while in combat, which of course does nothing then. The fact that the target bar is on by default for new frames is good, because it's important to be able to see party targets immediately in combat. Seems to me that the party frames are prepared "off-screen" in a "show player bar, show target bar" state, so that they are instantly ready when someone joins the party. They cannot have their visibility toggled while in combat.