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

Tooltips: General Usability Issues #47

Open
1 of 4 tasks
hexabits opened this issue Mar 21, 2014 · 4 comments
Open
1 of 4 tasks

Tooltips: General Usability Issues #47

hexabits opened this issue Mar 21, 2014 · 4 comments
Assignees
Milestone

Comments

@hexabits
Copy link
Member

Large tooltips like enum type descriptions can take a long time to load, and they are computed continuously as you hover. Take for example the Havok collision layers or materials. In the Type column, hover over the enum type and it will take a long time to load, and it never loads the same way twice. It's pretty much impossible to read and if it loads well, it might still disappear before you can even read it. I've already refactored the method some to deal with it, but it's not helping, as the sluggishness seems to stem from the UI having to parse such a large HTML table. The method is QString NifValue::typeDescription( const QString & typId ) in nifvalue.cpp

I propose a few options:

  1. A dedicated widget (like Inspector view) which displays the descriptions for highlighted cells.
  2. A button on the cell which opens a modal window with the description.

We could then keep the problematic descriptions from popping up in a tooltip and to view the descriptions you need to use another method.


Secondary Issues

Enum type descriptions are unordered too, because they are stored in a QHash.

Task List

  • Attempt to make tooltips more "stable" by improving their display/hide time or changing how they are toggled.
  • Consider moving certain tooltips to a widget or modal to improve usability.
  • Fix formatting issues with various descriptions.
  • Fix sorting issues with enum type descriptions and any others.
@neomonkeus
Copy link
Member

I had made a proposal to update the nif.xml structure to add a & attributes for cases like enum where there is alot of information present. It is also generally aimed at ensuring the quality of information within the nif.xml and seeing what is missing information. Would this help in that case as you could display the short description with an option to pull the more detailed version if needed, or is it just the same thing and would end up hiding information from the use.

@hexabits hexabits changed the title Sluggish Tooltips Tooltips: Slowness, formatting issues Mar 27, 2014
@hexabits hexabits changed the title Tooltips: Slowness, formatting issues Tooltips: Slowness, formatting issues, sorting issues Mar 27, 2014
@hexabits hexabits changed the title Tooltips: Slowness, formatting issues, sorting issues Tooltips: General Usability Issues Mar 27, 2014
@hexabits
Copy link
Member Author

Fixed the ordering problem in hexabits/nifskope@52f2f20

@hexabits hexabits added this to the v1.2.0 milestone May 17, 2014
@neomonkeus
Copy link
Member

With the port to Qt5, the font size seems smaller than before as reported by Hanaisse and verified.
Think we should we add an option to increase size for accessibility reasons, either specifically for this or global options.

@hexabits
Copy link
Member Author

It was an intentional change. The default was just too large. It was the only way to get large enums to fit. With that said I agree it's quite small, but tooltips are next to useless as currently implemented.

One can edit the QSS file in their install directory:

QToolTip
{
    opacity: 223;
    color: steelblue;
    border: 1px solid steelblue;
    border-radius: 5px;
    padding: 4px;
    background: ghostwhite;
    font-size: 10px;
}

... You just remove or change the font-size.

There is no way that I know of off the top of my head to make it an actual in-app option.


I think showing the help text in a status bar at the bottom of the window might be a good idea.

@hexabits hexabits mentioned this issue Jun 12, 2014
@hexabits hexabits modified the milestones: v1.2.0, v2.0.0 Nov 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants