nUI [Development] - Retail 

-------------------------------------------------------------------------------------------
-- 10.1.5.50006.0 PTR
-------------------------------------------------------------------------------------------
* nUI_Button.lua
> Error: 40x Interface/AddOns/nUI/Bars/nUI_Button.lua:255: Usage: GetActionInfo(slot)
> Added check for a null slot before using command

* nUI_Movers.lua
> Error: 1x GroupLootFrame1:SetPoint(): Couldn't find region named 'MirrorTimer1' [string "=[C]"]: in function `SetPoint'
[string "@Interface/AddOns/nUI/Plugins/nUI_Movers.lua"]:971: in function <Interface/AddOns/nUI/Plugins/nUI_Movers.lua:669>
> MirrorTimer1 potentially renamed to MirrorTimerContainer ( multiple Mirrors ?)

Additional Notes to previous notes:

1. The previous thought that the tooltip system was not working, could be due to this being the test server as
they add to the button text for reporting errors and so could be replacing the tooltip addition nUI creates.
It might not be something fixable based on conversations with others on the subject.

2. The micromenu has been altered in this patch and thus, nUI's version may have to be altered to match.

3. The edit mode system appears to override what nUI does. So, I will need to investigate how much work it will be to have
nUI override the edit mode instead, I suspect alot but I might be lucky. For now the best bet, if the nUI layout ( without the edit mode )
isn't what you expect, import the edit mode layout below into the edit mode system and apply it.

4. And Yes, nUI is getting harder and harder to fix. Especially when they are adding interface elements in patches now and not just expansions. nUI is almost hitting 20 and it might be time for it to retire. I am seriously looking at creating a replacement that is more up to date and hopefully more easier for someone else to take over when it is time for me to move on.



This is a copy of a recent nUI layout ( takes into account the new micromenu additions ( the eye ) and placement of the 3 additional action bars in a different location for those that choose to show them.)

0 39 0 0 0 7 1 MultiBarBottomLeft 213.0 4.0 -1 ##$$%/&*'%)$+# 0 1 0 7 7 UIParent -231.0 210.5 -1 ##$$%/&&'%(#,$ 0 2 0 3 5 MultiBarBottomLeft 4.0 -1.0 -1 ##$$%/&&'%(#,$ 0 3 0 6 6 UIParent 462.9 19.0 -1 #$$%%/&$'%(#,$ 0 4 0 8 8 UIParent -460.9 21.0 -1 #$$%%/&$'%(#,$ 0 5 0 4 4 UIParent -455.5 -249.6 -1 ##$&%/&#'%(#,$ 0 6 0 4 4 UIParent 366.0 -251.5 -1 ##$&%/&#'%(#,$ 0 7 0 7 1 MainMenuBar -272.0 4.0 -1 ##$&%/&#'%(#,$ 0 10 0 4 4 UIParent 157.0 -175.0 -1 ##$$&('% 0 11 0 7 1 MainMenuBar -50.0 4.0 -1 ##$$&('%,# 0 12 0 7 1 MainMenuBar 153.0 4.0 -1 ##$$&('% 1 -1 0 2 8 PlayerFrame -24.0 11.0 -1 ##$$%# 2 -1 0 5 5 UIParent -2.0 394.0 -1 #$$#%( 3 0 0 3 3 UIParent 356.0 -153.0 -1 $$3# 3 1 0 4 4 UIParent 313.0 -143.0 -1 %#3# 3 2 1 3 5 TargetFrame -10.0 0.0 -1 %#&#3# 3 3 1 0 2 CompactRaidFrameManager 0.0 -7.0 -1 '#(#)#-#.#/#1$3# 3 4 1 0 2 CompactRaidFrameManager 0.0 -5.0 -1 ,#-#.#/#0#1#2( 3 5 1 5 5 UIParent 0.0 0.0 -1 &#*$3# 3 6 0 2 2 UIParent -288.0 -143.0 -1 -#.#/#4& 3 7 1 4 4 UIParent 0.0 0.0 -1 3# 4 -1 0 7 1 PetActionBar -23.0 4.0 -1 # 5 -1 0 4 4 UIParent -342.0 -43.0 -1 # 6 0 1 2 0 MinimapCluster -10.0 -10.0 -1 ##$#%#&.(()( 6 1 0 2 2 UIParent -288.0 -36.0 -1 ##$#%#'+(()( 7 -1 0 0 0 UIParent 1350.0 -148.0 -1 # 8 -1 0 6 6 UIParent 11.2 89.7 -1 #&$}%$&7 9 -1 0 8 8 UIParent -464.5 211.0 -1 # 10 -1 0 2 2 UIParent -279.0 -79.0 -1 # 11 -1 0 5 5 UIParent -377.0 -206.0 -1 # 12 -1 0 5 5 UIParent -2.0 53.2 -1 ##$# 13 -1 0 4 4 UIParent 0.0 484.0 -1 ##$#%#&+ 14 -1 0 5 5 UIParent -16.0 -256.5 -1 ##$#%( 15 0 1 7 7 StatusTrackingBarManager 0.0 0.0 -1 # 15 1 1 7 1 MainStatusTrackingBarContainer 0.0 0.0 -1 # 16 -1 1 5 5 UIParent 0.0 0.0 -1 #( 17 -1 1 1 1 UIParent 0.0 -100.0 -1 ## 18 -1 1 5 5 UIParent 0.0 0.0 -1 #- 19 -1 1 7 7 UIParent 0.0 0.0 -1 ##



-------------------------------------------------------------------------------------------
10.1.5.49595.0 PTR
-------------------------------------------------------------------------------------------
* nUI_Integration.xml
> Added KeyBindings Functionality back into nUI (oops sorry)

Unfortunately due to the overhaul Blizzard did to the tooltip system in Dragonflight I have to take
a closer look at how to keep the nUI added Keybinding text on the mouseover tooltip.
You can still use the CTRL-ALT-RIGHT CLICK to activate the nUI keybinding box which clicked on
an nUI action button.

Note:
Action bars 6,7,8 are neither enabled or disabled by nUI so you can utilise those bars through the
edit mode system however you like.

Currently on 10.1.5 PTR the flyout spell buttons do not work as expected. This is a Blizzard related
problem as it happens when no addons are loaded.

If you have never set up your character/account with a copy of nui's editmode layout you can use the
below block of text to set one up.

If one exists but it isn't active, select it and do any other changes as you feel fine about. If necessary you can overwrite.


As a reminder, this is the EditMode Layout you can import to get any of the Blizzard frames in a location that is close to an nUI layout despite some of the frames not being in nUI's control.

0 35 0 0 0 7 1 MultiBarBottomLeft 213.0 4.0 -1 ##$$%/&*'%)$+# 0 1 0 7 7 UIParent -231.0 210.5 -1 ##$$%/&&'%(#,$ 0 2 0 3 5 MultiBarBottomLeft 4.0 -1.0 -1 ##$$%/&&'%(#,$ 0 3 0 6 6 UIParent 462.9 19.0 -1 #$$%%/&$'%(#,$ 0 4 0 8 8 UIParent -460.9 21.0 -1 #$$%%/&$'%(#,$ 0 5 0 6 6 UIParent 100.0 23.2 -1 ##$$%/&#'%(#,$ 0 6 0 8 8 UIParent -84.5 22.3 -1 ##$$%/&#'%(#,$ 0 7 0 7 1 MainMenuBar -272.0 4.0 -1 ##$&%/&#'%(#,$ 0 10 0 4 4 UIParent 157.0 -175.0 -1 ##$$&('% 0 11 0 7 1 MainMenuBar -50.0 4.0 -1 ##$$&('%,# 0 12 0 7 1 MainMenuBar 153.0 4.0 -1 ##$$&('% 1 -1 0 4 4 UIParent -21.0 -92.5 -1 ##$$ 2 -1 0 5 5 UIParent -2.0 394.0 -1 #$$# 3 0 0 3 3 UIParent 356.0 -153.0 -1 $$3# 3 1 0 4 4 UIParent 313.0 -143.0 -1 %#3# 3 2 1 3 5 TargetFrame -10.0 0.0 -1 %## 3 3 1 0 2 CompactRaidFrameManager 0.0 -7.0 -1 '#(#)#-#.#/#1$3# 3 4 1 0 2 CompactRaidFrameManager 0.0 -5.0 -1 ,#-#.#/#0#1#2( 3 5 1 5 5 UIParent 0.0 0.0 -1 &#*$3# 3 6 0 2 2 UIParent -288.0 -143.0 -1 3# 4 -1 0 7 1 PetActionBar -23.0 4.0 -1 # 5 -1 0 4 4 UIParent -342.0 -43.0 -1 # 6 0 1 2 0 MinimapCluster -10.0 -10.0 -1 ##$#%#&.(()( 6 1 0 2 2 UIParent -288.0 -36.0 -1 ##$#%#'+(()( 7 -1 0 0 0 UIParent 1350.0 -148.0 -1 # 8 -1 0 3 3 UIParent 34.0 -404.3 -1 #&$r%$&: 9 -1 0 8 8 UIParent -464.5 211.0 -1 # 10 -1 0 2 2 UIParent -279.0 -79.0 -1 # 11 -1 0 5 5 UIParent -377.0 -206.0 -1 # 12 -1 0 5 5 UIParent -2.0 53.2 -1 ## 13 -1 0 1 1 UIParent 6.0 -42.5 -1 ##$#%- 14 -1 0 5 5 UIParent -16.0 -256.5 -1 ##$#%( 15 0 1 7 7 StatusTrackingBarManager 0.0 0.0 -1 # 15 1 1 7 1 MainStatusTrackingBarContainer 0.0 0.0 -1 # 16 -1 1 5 5 UIParent 0.0 0.0 -1 #(

-------------------------------------------------------------------------------------------
10.1.5.49516.0 PTR
-------------------------------------------------------------------------------------------

* nUI_Bars.xml
* nUI_Button.lua
* nUI_SpecialBars.lua
* nUI_PetBar.lua
* nUI_PossessBar.lua
* nUI_ShapeshiftBar.lua
> Restored button bars back into nUI's control
> Hopefully finally fixed the annoying overlaying borders problem
> NOTE: You may find that some bars will have to be set up again
> NOTE: Flyout buttons don't work yet, so use the individual button rather than the flyout
> ALSO: Flyouts in Spellbook may be slightly off and not working as expected


IMPORTANT NOTICE:
>>> Objective Tracker <<<
I have kept the Objective Tracker in Blizzards control. This allows users to use their tracker of choice.

>>> Micro Menu <<<
I have kept the Micro Menu in Blizzards control, mainly because they have changed that module significantly.
This might change however once I figure the new changes out.

>>> Chat Frame <<<
nUI manages the chat frame as normal but because it isn't an nUI created frame it can be moved via Edit Mode
This frame may be the major factor to the taint errors.

>>> Unit Frames / Groups / Raids etc <<<
nUI still manages these all but are usually the targets for taint errors due to their normal in combat updates

>>> Override Action Bar <<<
Hopefully all will be well here now that we have gone back to nUI managing the bars.
This is usually where special combat situations fall over as the buttons aren't updated at the right time

>>> Minimap <<<
As per normal, minimap is under nUI control
Similar to Chat Frame this could be a major factor to the taint errors

>>> Minimap Button Bag <<<
Similar to Chat Frame and Minimap, nUI is managing the Minimap Button Bag

FEEDBACK:
Please can you give any feedback you have either on wowinterface or on curse. Curse has an issue database which makes tracking and dealing with those easier but either site is fine.

Dungeons and Raids are the most important avenues to check as I don't do them myself.