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

improve sign summary spacing #192

Open
kvesik opened this issue Aug 16, 2023 · 0 comments
Open

improve sign summary spacing #192

kvesik opened this issue Aug 16, 2023 · 0 comments
Labels
enhancement New feature or request GUI only Work on this issue might reference data structures, but won't affect them. (low priority)

Comments

@kvesik
Copy link
Collaborator

kvesik commented Aug 16, 2023

The visual sign summary panel in the main SLPAA window currently wastes a bit of space here and there. This should be addressed, because if the summary takes up a lot of vertical space the user may not be able to see associated Relation and Movement/Location modules get highlighted when they mouse over modules in the visual summary.

image

Ideas for reducing wasted space:

  • remove the blank line that currently shows up next to "Hand 1" and "Hand 2"
  • organize points and intervals more efficiently; I initially just put intervals on one (or more if necessary) lines, and points on a separate one (or more), but often we should be able to get both points and intervals on the same line
  • possibly reduce vertical height of rectangles/ellipses? or maybe make this a user setting? or maybe it depends on font size, which is a user setting? food for thought.
  • ... any more?
@kvesik kvesik added the enhancement New feature or request label Aug 16, 2023
@kvesik kvesik added (low priority) GUI only Work on this issue might reference data structures, but won't affect them. labels Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request GUI only Work on this issue might reference data structures, but won't affect them. (low priority)
Projects
None yet
Development

No branches or pull requests

1 participant