CommunityDKP

CommunityDKP

194k Downloads

Monolith's Options panel has ambiguous layout

thunk84 opened this issue ยท 1 comments

commented

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I've always found the Monolith options panel to be ambiguous. There are are multiple broadcast buttons, a save button that's required for some options but not others, etc that are generally in the vicinity of the items they operate on, but I'm never really clear, particularly with the save button, which options are associated with which button. Then there are so many pages of options to hunt through: There's an options tab. That has a Modes button, that opens a new window with two tabs.

I don't have to click Save Settings if I adjust the boss kill bonus, but I do have to click it if I adjust the Loot history limit slider. But the Save Settings button is not really located next to the settings. It's close by, but so are the Wipe Table and Move Bid Timer buttons, that arguably are not associated with the sliders and check boxes.

All in all, Mono introduced a lot of settings spread across a lot of pages. I frequently have to walk officers through the settings pages to find the things they're looking for.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I believe the following would help make the options more readable (and easier to find things):

  1. The broadcast settings button on the dkp modes tab mentions that it actually broadcasts some stuff from options and some stuff from modes tabs. And we have separate buttons for broadcasting min and max dkp values. So, do we really need 3 separate broadcast buttons? Unless there's a technical limitation in transmitting settings, it would be preferable to have one broadcast button that sends everything. I'm finding officers are usually clicking all three anyway, regardless of what they change, because they don't clearly understand the differences.

  2. Likewise, add a border around the settings and Save Settings button that go together. I'm unclear on which options require the Save Settings button. For example, changing boss dkp award does NOT require clicking the Save button, but changing the history slider does. Changing settings on the dkp modes tab does not appear to need the save button. So it would be helpful to clearly group the settings that require Save Settings button in a box (or better yet, automatically save all settings and remove that Save button altogether). The save button is in the vicinity of the sliders, but it's right next to the Wipe Tables and Move Bid Timer buttons, that makes it appear to a global save button applicable to all settings.

  3. The DKP modes pane with two tabs is pretty confusing. It makes for a lot of clicking when hunting for settings if you don't remember where they are already. I would suggest at least condensing the whitespace on the Modes tab a little bit and moving all the "misc" tab check boxes onto the Modes tab. That would at least reduce the number of pages the user has to move through. And better yet, maybe remove the Modes button altogether and make it a tab between "options" and "loot history"

image

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

commented

This is part of a larger effort, which will eventually become CommunityDKP Version 4, which is an entirely new UI. Working with Addon UI in LUA as it relates to WoW's Addon Interface is not exactly easy. The amount of work needed to make these panels a little more user friend (which I admit need to be) would be better served in doing a total overhaul of the UI itself.

We've setup a project to track all feature requests that we feel fall into this, so that as we start to gain steam and a backlog for what Version 4 might look like, we have a place to organize ourselves.

This feature request has gone into that project.