|
phoenix599
|
First, thank you very much for CTMod...it is fantastic!
After I installed the latest patch this morning, it appears that only the rogue actions that require stealth do not work on any action bar! I will continue to test this evening, but I logged out/on, logged off/on, switched bars/icons, everything, and they don't appear to work. In addition, the tool tips for rogue "requires stealth" actions don't seem to appear either. I have mapped these functions to the numeric keypad for the time being, and they work fine with key mapping. All other rogue actions that do not require stealth work fine, and their tool tips also display properly. I know this sounds crazy...but that is what appears to be happening on my system.
Thanks in advance for your help!
|
|
dargen
|
I just tried it on my rogue and it seems to be working ok for me. I placed Ambush (which requires stealth) on each of the bars. While stealthed I was able to see the tooltip for the button, click the button, and use the hotkey for the button on each of the bars.
First please verify the version of CT_BottomBar that you are using by going into the game, typing /ct, and then looking at the version numbers shown beside the addon names. The CT_BottomBar version should be 3.301.
Next try disabling all addons except for CT_BottomBar, and then let me know if the issue still occurs for you. If it works after disabling all other addons, then there may be an issue which only shows up when two or more addons are enabled at the same time. To work out which addons are involved, you'll need to enable a few addons at a time and test to see if the issue occurs. If the problem doesn't show up, then disable those addons, enable some others, and check again, etc until you've got it narrowed down.
If you want to provide a list of the addons you're using I can take a look as well. You can find a list of your addons in the "World of Warcraft\WTF\Account\<account name>\<server name>\<character name>\AddOns.txt" file. Unfortunately that file doesn't include any version numbers, but you can open with notepad, select all the text, and then copy and paste it into a reply.
|
|
phoenix599
|
Dargen,
Interesting observation FYI. I have BB v3.301. When I moved the one bar that I am having this issue with slightly more above the bar upon which I had it nested, the tool tips and buttons appeared and worked. When I moved the same bar over another bar that I have along the bottom of the screen and nested it as close as I had with the other two originaly, it still functioned properly! As strange as this sounds, it appears to be this one area on the screen which might be causing this issue (lower right hand portion). I will continue to test and let you know what I observe. And thank you very much for the rapid response!
|
|
dargen
|
It sounds like you might have an invisible frame in one area of your screen, which is preventing the mouse pointer from coming in contact with anything below that frame. Does it work ok if you move the bars to a different part of the screen?
There is a command in the game called /framestack, which might help diagnose your issue. When you move your mouse over a UI element, a tooltip will appear in one of the four corners of your screen. That tooltip contains a list of the frames that are stacked below your mouse pointer (and it also shows the coordinates of the mouse pointer). For each frame below the mouse pointer, it shows the frame's level number (for example, <0> is frame level zero) and the name of the frame (or something like "table: 150E4560" if the frame does not have a name).
All UI elements in the game are based on rectangular frames. Just like a stack of papers, you can also have a stack of frames. Each frame has a level number assigned to it, with the lowest one being the "WorldFrame" at level 0 (the bottom of the stack).
The button you can't click is probably at a lower frame level than this invisible frame. However, simply being at a lower level isn't enough to prevent a click from reaching the button. To block mouse contact with the button, the frame sitting at the higher level would also need to be configured to trap all mouse clicks and movement when the mouse is over the frame.
By moving the mouse around and examining the names of the frames that appear in the framestack tooltip, you may be able to deduce which addon created the frame in the area of the screen where you are having the issue.
One thing to keep in mind is that not all frames trap the mouse. If you want to see if a particular frame is trapping the mouse, you can use a command similar to the one shown below. The command will display "empty result" if the mouse is not being trapped, and "[1]=1" if it is being trapped.
/dump MyFrame:IsMouseEnabled()
In the above example, the name of the frame I used is "MyFrame". This command will only work for frames that have a name. It won't work for the ones that look like "table: 150E4560" in the framestack tooltip. Be sure to type everything correctly, including using upper/lower case letters, otherwise you'll probably get an error message.
|
|
phoenix599
|
Dargen,
You may be on to something. I will test and let you know what I find out. Thank you very much for your rapid response and expert advise.
|
