Rogue and Druid

[Galahad]

I am having problems with my Rogue and Druid characters. When I go stealth with the Rogue and I go into combat and the stealth goes away the Interface tells me I have to be behind the target when I use my keyboard keys, but it works just fine with me using my mouse. A similar thing happens when I switch forms on my Druid, once I switch forms and go back to human form the Interface tells me that I can not use my action bar in that form using the keyboard, but agian it works when I use the mouse.

I am just wondering if there is a way to fix that problem, or if there is something that maybe I missed. Thank You.

[Xrystal]

I think there was a thread somewhere around here discussing this but I can't remember what was said or where it is. I'll do a quick search around and see and post it here.

Edit: Okay, that description seems to fit the keybinding issue we have been seeing more often since 3.3 due to WoW taking control back unexpectedly. The way nUI works at present wasn't prepared for this I believe and Scott is trying to locate where and how to resolve it without customizing the whole button system if I remember rightly. Anyway here's the post discussing the problem. http://www.wowinterface.com/forums/s...ad.php?t=30079

[Taralas]

Yep. Sadly this has been going on for quite a while. Any time that the Blizzard UI remaps the keys from the default action bar to any other bar, be it a Vehicle Bar, a stance bar, or a 'possession' bar, it does not perform a switch back to the standard bar if the original switch and the end swtich both take place during combat.

-Taralas

[Galahad]

Well thanks guys for the info, guess I will wait and see when and if the problem is fixed.

[Wiggleadin]

This is the same problem I've been having. /console reloadui helps, but reloading everytime I stealth/get out of a vehicle/etc is troublesome.

Any ETA on a fix for this?

[Xrystal]

Scott is doing his best to work on what may be a fix. Once he releases a new version can you guys test it out please.

Hopefully if you can consistently repeat the problem and the problem goes away after his attempt at fix is set up then that could mean the cause has been found in the code. We know the cause itself but looking at several thousand lines of code doesn't make it easy.

[spiel2001]

Yeah -- I thought I was going to get a fix out this week, but I still can't pin down the cause. I plan on working on it some more after work this evening. As soon as I can pin it down, I'll get an update out.