You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reporting an issue, please try to reproduce the issue with just Dominos and Dominos_Config running. Dominos reuses a good chunk of the stock UI, and other popular addons, like Move Anything, like to take control of those parts, too.
action bar 1 and 2 are somehow paging with each other or something...
this has happened twice now, 3 days apart - both inside high rated arena matches causing me to lose the game
only relogging will fix it. Addon Version
You can get this via running /dominos version in game
10.2.36-cata World of Warcraft Version
For example, Classic, Retail, PTR, Beta.
cata
image after bug
and now after relogging to fix it
bars are back to normal. there are no paging settings on either bar.
have a video of it happening but i cannot see anything unusual happening.
The text was updated successfully, but these errors were encountered:
None of the Quick Paging settings are enabled? Historically, most of these cases have been due to pressing either Shift + 1/2/3/4/5/6 or Shift + Mouse Wheel. I would also try removing these specific bindings:
When reporting an issue, please try to reproduce the issue with just Dominos and Dominos_Config running. Dominos reuses a good chunk of the stock UI, and other popular addons, like Move Anything, like to take control of those parts, too.
action bar 1 and 2 are somehow paging with each other or something...
this has happened twice now, 3 days apart - both inside high rated arena matches causing me to lose the game
only relogging will fix it.
Addon Version
You can get this via running
/dominos version
in game10.2.36-cata
World of Warcraft Version
For example, Classic, Retail, PTR, Beta.
cata
image after bug
and now after relogging to fix it
bars are back to normal. there are no paging settings on either bar.
have a video of it happening but i cannot see anything unusual happening.
The text was updated successfully, but these errors were encountered: