GUI Improvements

[5HT2]

For after #1510 is merged.

• [ ] HUD Grid to make aligning hud components much easier.
  • [ ] Maybe with customizable size (eg 5px)
  • [ ] Preview
  • [ ] When holding alt
• [ ] Auto docking
• [ ] Themes (Formerly #32)
• [ ] "Categories" for different things
  • [ ] Switching via icons at the top
  • [ ] HUD
  • [ ] Client related settings
  • [ ] Button to set all module visibility to false
  • [ ] Friends manager
  • [ ] Alt manager
  • [ ] Macro / script (#1367) editor
• [x] Option to display modified settings in a bold font
• [x] Descriptions for settings
• [x] Frequently used / Favorites
• [ ] Target Hud (#1529)
• [x] Customizable Item Count
• [x] Radar
  • [x] Player / hostile / passive / neutral options
  • [x] Newchunks option
• [ ] Potion UI
• [ ] User custom module categories
• [ ] Make window corner roundness customizable
• [ ] Readd old module list options
  • [ ] > Arrow option
  • [ ] Custom color gradient (up to 5 colors)
  • [ ] Category color options
  • [ ] Custom rainbow options such as saturation
  • [x] Custom single color
  • [ ] Cycling saturation option for a single color
• [x] Legacy text radar

[omninope]

Suggestions:

• Ability to keybind Hud elements. Useful because some things like CombatItemCount, CrystalDamage and Targethud (when it gets implemented) are only used in combat an a bind is easier and faster than making another profile and loading it, especially when the player needs to engage in combat immediately. Done in commit d0a78db1d1d6f7af1a1c82f914578e74931c3947
• Ability to input negative ammounts. Useful for things like ItemModel.
• Maybe less useful: Ability to scale InventoryViewer separately, because people with lower resolution monitors may want their GUI small but still want to clearly see what is in their inventory. Done in commit f49ca78deda6ac2891399cd0bd1c63b842b93d44.

[5HT2]

Ability to input negative ammounts. Useful for things like ItemModel.

This isn't a GUI thing as much as it is a setting thing. None of the settings allow negative values, though they could.

I think a power user solution would be to allow the user to set any value with the ;set command, ignoring the gui limits. If someone is using commands and they mess up, it's their fault.

Future does the same thing as well. I think it's the easiest way to idiot proof the GUI while allowing power users to set whatever they want

[Luna5ama]

Ability to input negative ammounts. Useful for things like ItemModel.

This isn't a GUI thing as much as it is a setting thing. None of the settings allow negative values, though they could.

I think a power user solution would be to allow the user to set any value with the ;set command, ignoring the gui limits. If someone is using commands and they mess up, it's their fault.

Future does the same thing as well. I think it's the easiest way to idiot proof the GUI while allowing power users to set whatever they want

No. It always allow negative number if the range allows. And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.

[5HT2]

And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.

That's fine imo. If the user uses a set command or something to set a value out of range that's their fault.

[Luna5ama]

And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.

That's fine imo. If the user uses a set command or something to set a value out of range that's their fault.

It isn't. If it causes crash then resetting the value will be pain. You have to go into the config and search then edit it manually. 🗿

[5HT2]

Okay I guess