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

Suggestions & Issues After Much Use #153

Open
CoreAutomation-JD opened this issue Nov 27, 2023 · 0 comments
Open

Suggestions & Issues After Much Use #153

CoreAutomation-JD opened this issue Nov 27, 2023 · 0 comments

Comments

@CoreAutomation-JD
Copy link

CoreAutomation-JD commented Nov 27, 2023

  • It would be very nice to have a user preference to turn off tooltips. When doing a large amount of item or spell cloning they often get in the way.
  • The spell/item icon flyout either requires you to immediately mouse over the newly presented UI, or wait for it to display, hover over it (causes it to dismiss), then click the icon to open the flyout again. Removing mouseover and using an implicit button to close or open would be ideal, or otherwise, not registering the flyouts mouseover event handler until it has fulled rendered.
  • The UI for showing spell graphics could use a column amount icon - Viewing 2 columns in 4k will crash the tab about 1/3 of the time I use it, even on a very beefy machine.
  • The temporary modal when holding the control key is useful the first time, after that it is intrusive when doing a lot of copy and paste of text in particular. A user preference to disable it would be handy.
  • Cloning items over and over eventually runs into considerable caching issues (Pulls up an incorrect detail view vs. what is shown in search results). I have been creating armor sets for my next update, and a lot of that includes cloning previously created items. Quite often item names in particular get cached. This is no rhyme or reason to this from a user perspective, but it happens consistently. I assume you are pulling response data after a write when a user saves a new / updated item or spell and merging into some form of state as opposed to re-running a query. Something is definitely going on here.
  • With multiple tabs open, often all viewing the items or spell search UI, eventually I will hit significant caching issues. For instance, I have cloned many items only to realize the cloned value uses cached data as opposed to actual current record data.
  • The lore field is still causing tabs to crash when edited and then trying to clone the recently edited item.
  • Saving a new item requires two clicks to get back to your previous view.
  • It would be nice to setup a basic scheduled backup that runs each night. If we can also indicate an optional folder to save to even better.
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

No branches or pull requests

1 participant