nUI5 and WoW 4.2 Compatibility

[Daveo77]

Hi.

Will nUI5 continue to work when patch 4.2 goes live (due within the next two weeks) ?

[spiel2001]

I don't anticipate a problem.

[Blanckaert]

Originally Posted by spiel2001 I don't anticipate a problem.

Cool... and if there is, I am sure Scott will burn the midnight oil, and get a 'fix' out... Unless of course, he has nUI6 just laying around waiting to be brought out front and centre....

But there might be a slight issue of 'load out of date' addons... (but I guessing, I'm just a user....)

[Daveo77]

Originally Posted by spiel2001 I don't anticipate a problem.

OK, thanks Scott.

[Xrystal]

gimme a shout if things go crazy .. I don't really play much anymore but will log in and make sure my addons and nUI work reasonably well haha

[Xrystal]

Okay, decided to log in and check some stuff out and managed to get m test install updated with 4.2 and nUI and my related addons installed.

Test 1 : nUI, Addon Loader and Bugsack only loaded ..
Result: Looks like it works but noticed bag bar not displaying.

[Seer]

might be because of the removed key ring. (didn't notice that one myself last time I was on the 4.2 ptr..)

Weird that the top button works, since the made a new button for the journal.

[Xrystal]

ah, thats why i got some gold in my game mail about keys

and yeah, all the buttons at the top worked

[Xrystal]

This change in nUI_BagBar.lua fixes the problem and should *not tested yet* work in 4.1 as well.

PHP Code:

if _G["KeyRingButton"] then
    nUI_BagBar.Buttons[1] = _G["KeyRingButton"];
    nUI_BagBar.Buttons[2] = nUI_ButtonBagButton;
    nUI_BagBar.Buttons[3] = _G["CharacterBag3Slot"];
    nUI_BagBar.Buttons[4] = _G["CharacterBag2Slot"];
    nUI_BagBar.Buttons[5] = _G["CharacterBag1Slot"];
    nUI_BagBar.Buttons[6] = _G["CharacterBag0Slot"];
    nUI_BagBar.Buttons[7] = _G["MainMenuBarBackpackButton"];
else
    nUI_BagBar.Buttons[1] = nUI_ButtonBagButton;
    nUI_BagBar.Buttons[2] = _G["CharacterBag3Slot"];
    nUI_BagBar.Buttons[3] = _G["CharacterBag2Slot"];
    nUI_BagBar.Buttons[4] = _G["CharacterBag1Slot"];
    nUI_BagBar.Buttons[5] = _G["CharacterBag0Slot"];
    nUI_BagBar.Buttons[6] = _G["MainMenuBarBackpackButton"];
end 


[Daveo77]

Hi Xrystal

One thing I've noticed in your screenshot is that due to the extra button in the console (Encounter Journal), the Latency and FPS bars appear to overlap the edges of the micro menu container.

I'll make the above change to my copy of nUI_BagBar.lua and test it on 4.1.

--EDIT--
OK, above code change to nUI_BagBar.lua works fine on 4.1

[Xrystal]

Yeah I saw that overlap problem too, it might be the case that the written info will have to be placed elsewhere or as a button themselves rather than words.

[spiel2001]

Yeah... I'll address it with a scaling or position change.

[spiel2001]

Is the PTR down? I can't seem to access it -- it want's to patch me, but the download won't start. Dunno if it is me or the PTR.

[Xrystal]

It let me download the patch earlier Scott, but wasn't on there long.

[spiel2001]

Well... it finally let me download the patch. So, looking it all over now.

[Xrystal]

What I did.

1. Patched to 4.2
2. Cleared Addon and WTF folder (apart from main 2 wtf files)
3. Redownloaded or moved across latest addons
4. Restarted WoW with no addons activated.
5. No errors noticed.
6. Restarted WoW with Bugsack activated.
7. No errors noticed.
8. Restarted WoW with Bugsack, ACP activated.
9. No errors noticed.
10. Restarted WoW with Bugsack, ACP and nUI activated.
11. No errors noticed.
12. Restarted WoW with Bugsack, ACP, nUI and AuraButtons activated.
13. Screenshot 1 - Combat Log Window moved.
14. Moved Combat Log Window back into place
15. Restarted WoW with Bugsack, ACP, nUI, AuraButtons and skada.
16. Screenshot 2 - Combat Log Window moved again.

At no time did Bugsack located any errors.

I use smallest UI Scale in windowed mode and always have since I started playing WoW.

[spiel2001]

OKay... I just got home from work, so I'm getting the patch now. Will get on it as soon as I can get online.

[Xrystal]

Good news is a reloadUI doesn't mess it up, only if you log out to at least character selection screen. Sounds like this could simply be the case of the values being saved to the config-cache.txt ( or whatever the window layout file is called ) incorrectly.