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

Improvement to View Options #723

Open
windymilla opened this issue Jan 31, 2025 · 1 comment
Open

Improvement to View Options #723

windymilla opened this issue Jan 31, 2025 · 1 comment
Labels
future feature New feature or request, but not core

Comments

@windymilla
Copy link
Collaborator

The manual suggests a method of making bookloupe messages manageable, which is often used by PPers:

  1. Hide all messages
  2. Turn on the first message type
  3. Look to see if any messages appear
  4. If so, fix, or remove the message
  5. When you have no messages left, turn on the next message type and go back to point 3
  6. When there are no more types left, you are done.

However, in any project, there are normally quite a few message types for which there were no actual messages, hence the need for point 3. It would be nice if either the toggle buttons for that message type were grayed out meaning "no point in you changing this as there aren't any of those", or maybe a single checkbox in the dialog, something like "Disable unused message types"

Alternative could be to "Hide unused message types". This has the advantage of making the dialog less busy, but the disadvantage that users may get familiar with where specific buttons are, e.g. bottom of the second column. Would certainly need to be a toggle, rather than permanent behavior.

@windymilla windymilla added the future feature New feature or request, but not core label Jan 31, 2025
@srjfoo
Copy link
Member

srjfoo commented Feb 2, 2025

I like the idea of having "Hide unused message types". And yes, I'd recommend it beig a toggle, and not sticky.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future feature New feature or request, but not core
Projects
None yet
Development

No branches or pull requests

2 participants