Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI/UX improvements #17

Merged
merged 9 commits into from Mar 17, 2023
Merged

UI/UX improvements #17

merged 9 commits into from Mar 17, 2023

Conversation

PrincessRTFM
Copy link
Collaborator

@PrincessRTFM PrincessRTFM commented Mar 16, 2023

Changes made:

  • [OBSOLETED BY LATER CHANGE] There are two buttons to locate the hunt mark on your map. One shows a radius for the approximate area, one shows only a map marker, but both used the same tooltips, which could be confusing for new users. The button that includes the radius now says "show hunt area on the map" while the one with only a single marker still uses the word "location" as before.
  • There's a new subcommand argument local to toggle the display of the local map zone's hunt targets window, instead of needing to open the main window, open the configuration, toggle the box, and close the configuration.
  • The ability to lock window size/position was implemented to prevent accidentally moving the windows while attempting to click on the controls.
  • The main window's tree display of hunt marks per zone no longer indents the line with the mob name and utility buttons, reducing the required width of the window for people who keep it narrower to conserve space or fit their UI layout. It should still be clear that those lines are children of the relevant tree node thanks to the utility buttons. If this is not desired, it should be easy to revert, since the relevant two lines in Interface.cs (96 and 202) were only commented out, not deleted.
  • The two buttons to locate the mobs on the map have been condensed into one that performs a configurable default of either marker-and-area or marker-only, and performs the alternate action when shift is held while clicking. This will conserve more screen space and allow people to ignore the mode that they rarely/never use while still allowing everyone to select their preference and access the alternative with ease.
  • There's another new subcommand next to place a marker on the next hunt mark location. If there are any in the current zone, the nearest (two-dimensional euclidean distance) will be selected. Otherwise, if there are any hunts in the current expansion's other zones, one of them will be selected at random. Finally, all hunts anywhere in the world will be considered, and one of them will be selected at random. If other zones had to be examined for hunt marks, the main map will be opened to the appropriate zone. This also closes Feature Request: /command to "Place Marker on Map" for nearest/next Hunt. #14.

@PrincessRTFM PrincessRTFM marked this pull request as ready for review March 16, 2023 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request: /command to "Place Marker on Map" for nearest/next Hunt.
2 participants