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

Missing Ellipsis in Menu Items #4969

Open
4 tasks done
Nerixyz opened this issue Nov 16, 2023 · 3 comments
Open
4 tasks done

Missing Ellipsis in Menu Items #4969

Nerixyz opened this issue Nov 16, 2023 · 3 comments

Comments

@Nerixyz
Copy link
Contributor

Nerixyz commented Nov 16, 2023

Checklist

  • I'm reporting a problem with Chatterino
  • I've verified that I'm running the most recent nightly build or stable release
  • I've looked for my problem on the wiki
  • I've searched the issues and pull requests for similar looking reports

Describe your issue

The split menu (when right-clicking on the split header or clicking on the kebab menu) contains an entry called Set filters, which opens a dialog to configure the filters. As per Apple's Human Interface Guidelines, it should have an ellipsis character added to signify that a dialog requiring user action will open. It should be Set Filters… although as Chatterino doesn't seem to use title case, it should be Set filters….

Append an ellipsis to a menu item’s label when people need to provide additional information before the action can complete. The ellipsis character (…) signals that another view will open in which people can input information or make choices.

Screenshots

OS and Chatterino Version

Chatterino 2.4.6 (commit 5693927) built with Qt 6.5.0, MSVC 193732825

@Nerixyz Nerixyz added the issue-report An issue reported by a user. label Nov 16, 2023
@pajlada pajlada added ux good first issue and removed issue-report An issue reported by a user. labels Nov 17, 2023
@x9136
Copy link

x9136 commented Nov 17, 2023

You will have to revise all the items in all the menus to solve this problem. Even in the screenshot at the beginning of the topic you can make the following changes:
Change channel → Change channel...
Open in streamlink → Open in streamlink... (When Preferred quality is set to Choose)
How to... → How to

In any case, if you do this, don't forget the recommendations for Windows as well. This one or maybe this one.

@Nerixyz Nerixyz changed the title Missing Ellipsis in 'Set filters' Menu Item Missing Ellipsis in Menu Items Nov 17, 2023
@ScrubN
Copy link
Contributor

ScrubN commented Dec 1, 2023

I made some progress on this, however some string literals (like Open in streamlink) are #defines inside CommomTexts.hpp. I saw #4896 mentioned working towards moving away from this style, so I wanted to ask how I should go about making the alternative versions with ellipses.

@Nerixyz
Copy link
Contributor Author

Nerixyz commented Dec 1, 2023

I made some progress on this, however some string literals (like Open in streamlink) are #defines inside CommomTexts.hpp. I saw #4896 mentioned working towards moving away from this style, so I wanted to ask how I should go about making the alternative versions with ellipses.

In my opinion, you can define the constants in the file they're used in (or you can inline them). So, for example, Open in streamlink… should be defined in SplitHeader.cpp. As this define is still used in Toasts.cpp (where it shouldn't have an ellipsis), it can [at least for now] be left in CommonTexts.hpp, although you could inline it there too if you want.

You can define a constant QString like this: const QString MY_STRING = u"my string"_s; - make sure common/Literals.hpp is included, and you're using namespace literals (or chatterino::literals in an anonymous namespace).

If you don't need the full string or want to add something (e.g. you want to call .arg(...)), you can create a constexpr QStringLiteral MY_STRING = u"foo %1"; (this isn't useful for the menus, however).

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

4 participants