![]() ![]() The Raid Settings tab has a wrong priority, it always goes under the raid frames, in bigger groups it makes it inaccessible, you have to move your ui to access this which is really annoying when you play with a big group and you are trying to manage 30 people in the raid. Some if not ‘most’ of the people prefer having the first buttons in an action bar on the very top so the spells are visible while right now they move to the bottom and when people change binds they run into issues while questing and don’t know what to do and why these binds are there. Let us choose if the action bar rows align to the top or the bottom to reverse the logic if need. This image is an example but you can imagine the quest buttons being a shift+, ctrl+, mouse buttons etc. Then the bottom part of your action bar is going to be used for quests and sometimes binds you need to use in your quests are going to be really annoying and questing will be a pain: When you rebind it so your most used binds are on the top: ![]() After that your main binds will show up on the bottom instead of the top. When you try to customize your UI and change the number of rows your UI will move the elements from left to (bottom) right. Most of us bind our most used spells in the action bar 1, the binds are 1-5 etc. The action bar is actually Action bar 1, no surprise right? The issue here is with how the action bar changes when you mess with ‘rows’ setting in Edit Mode. This is one of the issues that annoy me the most, as a player you don’t know which buttons/binds are going to be used during questing when you’re in a vehicle. Leave the Buffs setting always visible but make it gray and unclickable. When you switch to Buffs On Top setting and uncheck Use Larger Frame the Buffs settings will completely disappear from the window. This might be really confusing to people first time using this (including me when i got back to the game). However this setting is always active and the game remembers what you’ve chosen. The ‘Buffs On Top’ setting is inaccessible, you need to first check ‘Use Larger Frame’ to access the setting. Also sorry to mods for putting in links but this post would have no meaning without examples. I would love to see some forum mod noticing my message and maybe spreading the word about the bugs. ![]() I hope more people will notice this post and appreciate my efforts. I went through all of the settings to customize my game and here is what i found. I always pay attention to the UI the most so I don’t overload my screen with 100 UI elements and keep it simple and symetric/aligned, i always wanted to play the game with classic vibe but still be able to customize it. WoW is my favourite MMORPG game and I really want this game to get better. I was tired that i had to use addons to play wow the way i want, right now i can play with barely any addons and enjoy the game, however i found some issues with the new settings and i would love to use the moment when Blizzard do changes to UI and overal look of the game to let you guys know my thoughts. You can access the complete repository here.I came back to the game after a long break and i was really excited to see the new UI changes and all of the settings changes. import export default App Īnd you’re all done! Now, anytime you have a form dialog, all you need to do is to use the new custom dialog and pass it the loading prop. Let’s create a new Dialog.js component that inherits from Material Dialog and uses a LinearProgress component. Setup React ProjectĬreate React App and install React Material npx create-react-app react-material-dialog npm install Create a Custom Dialog ![]() This way, we have a consistent experience in every dialog without any redundancies. Here is an example I created using Material Linear Progress:īut what if we have other form dialogs in a project that requires to behave the same way? In this article, I will go through a step-by-step guide to creating a reusable custom dialog that inherits from React Material and extends functionality to include a built-in loading bar. A common example would be a newsletter subscription dialog, whether or not users choose to subscribe, they shouldn’t have to navigate back to the initial page.Ī good practice is to trigger a loading bar as soon as the user submits a request to the server. Form dialogs are very common and useful especially when you don’t want to redirect the user to a separate page. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |