nUI [WotLK Classic]

================================================================
3.4.3.51666.0 - WotLK Classic
================================================================
* nUI_PetFeeder.lua - Added C_Container to container frame functions
used when feeding the pet to fix the following error messages.

1x nUI/Plugins/nUI_PetFeeder.lua:503: attempt to call upvalue 'GetContainerItemLink' (a nil value)
[string "@nUI/Plugins/nUI_PetFeeder.lua"]:503: in function `FeedPet'
[string "@nUI/Units/nUI_UnitHappiness.lua"]:685: in function <nUI/Units/nUI_UnitHappiness.lua:683>

1x nUI/Plugins/nUI_PetFeeder.lua:501: attempt to call upvalue 'GetContainerNumSlots' (a nil value)
[string "@nUI/Plugins/nUI_PetFeeder.lua"]:501: in function `FeedPet'
[string "@nUI/Units/nUI_UnitHappiness.lua"]:685: in function <nUI/Units/nUI_UnitHappiness.lua:683>


* nUI_UnitFeedback.lua - Changed Arcane hit type from 65 to 64 - to fix the following error message

1x Usage: self:SetVertexColor(color [, a])
[string "=[C]"]: in function `SetVertexColor'
[string "@nUI/Units/nUI_UnitFeedback.lua"]:1029: in function `updateFeedbackFrame'
[string "@nUI/Units/nUI_UnitFeedback.lua"]:850: in function `newUnitInfo'
[string "@nUI/Units/nUI_UnitCache.lua"]:586: in function <nUI/Units/nUI_UnitCache.lua:530>

* nUI_Hud.lua - Defaulted offset of Hud by 100 so that the range appears above the action bar area.

Let me know if this causes other display issues my quick test didn't see.
Test involved killing lots of critters at level 21 rofl

================================================================
3.4.2.50664.0 - WotLK Classic
================================================================
* nUI_Integration.xml - commented out Keybinding.xml
* localization files - added Binding.xml category constants
* nUI_ButtonBar.lua - commented out references to nUI Keybinding
* nUI_HUD.lua - commented out references to nUI Keybinding
* nUI_InfoPanel.lua - commented out references to nUI Keybinding
* nUI_UnitPanel.lua - commented out references to nUI Keybinding
> Disabled nUI's keybinding for the moment due to conflict with Blizzards system.

================================================================
3.4.1.47720.0 - WotLK Classic
================================================================
* nUI_ShapeshiftBar.lua
> Addition to the cheating hide the extra border by setting the alpha to 0 trick rofl.

This covers warriors stances and hopefully Paladins and Druids ( stance bar and shapeshift bar uses same code )


================================================================
3.4.1.47612.0 - WotLK Classic
================================================================
* nUI_Button.lua
* nUI_BagBar.lua
* nUI_PetBar.lua
> Hide the extra border on the buttons by setting the alpha to 0

It's a dirty fix, but it appears to work. Hopefully, whenever I get around to rebuilding nUI from the ground up,
this issue will be fixed.

* nUI_InfoPanel_CombatLog.lua
> Fixed error : 0/1 to false/true

There are probably more similar to this that my limited testing didn't come across.

Note: There may be other problems related to the changes added in this patch. Rumors are that SOME of the Dragonflight API has been added to the game.

Testing: I only gave this a basic test. Log in.test dummy/simple combat and a few windown open/close tests. Let me know if you come across other issues during your gameplay.

================================================================
3.4.0.47168.0 - WotLK Classic
================================================================
* nUI_Movers.lua
> Added LootFrame, MasterLooterFrame and the 4 Group Loot Frames to the Mover system.

Please note that this ignores the open loot frame at current mouse position setting in the options screen.

The new default position starts just below the top bars and the frames can be moved using /nui mover.
I haven't been able to test the Master and Group Loot frames but I assume they will work
similarly to the solo loot frame.

================================================================
3.4.0.46902.0 - WotLK Classic
================================================================
* nUI_UnitRunes.lua
> Had to make some adjustments to the 7.2.5 and 8.0.1 additions
to make the rune buttons show and operate as expected.

================================================================
3.4.0.45942.1 - WotLK Classic
================================================================
* nUI_ButtonBar.lua
> Oops, did a thorough check comparison and found I had missed
some code out for the vehicle/override etc bar changes

*nUI_Button.lua
> Added code from retail that utilised the button update cycle to
give more accurate button statuses.



Thanks to redrumjay's (on Curse) testing of their equivalent update, so *fingers crossed* that this will have the action bars working in a similar way to retail including vehicle and override bars.

The stealthed bar switch in combat issue that was fixed in retail works in wrath but, wrath doesn't switch to the shadow bar so your spells aren't there.

This happens without nUI loaded so isn't a fault of nUI.

================================================================
3.4.0.45942.0 - WotLK Classic
================================================================
* nUI_ButtonBar.lua
> Forgot to add vehicle and override and possess bar switching to action bars
> Untested as I don't play classic

================================================================
3.4.0.45327.0 - WotLK Classic PrePatch Version
================================================================

* nUI_ButtonBag.lua
> Tracking Minimap Button had a name change - from MiniMapTrackingFrame to MiniMapTracking

* nUI_Minimap.lua
> WorldMap Minimap Button was sized for some reason which was making the display wrong


================================================================
3.4.0.44930.0 - WotLK Classic PrePatch PTR Version
================================================================
Based on nUI Classic Version : 2.5.1.38988.0

Changed TOC to WotLK Classic
30400 > 3.4.0 patch

* nUI_Minimap.lua
> Added WatchFrame to the test for which objective tracker we are using as Blizzard changed the name.