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

Display toast notification when toggling AVIM if toolbar button is hidden #110

Closed
1ec5 opened this issue Nov 27, 2014 · 1 comment
Closed

Comments

@1ec5
Copy link
Owner

1ec5 commented Nov 27, 2014

If AVIM’s toolbar button is hidden or in the application menu, toggling AVIM via the double Ctrl shortcut has no visible effect. There’s an audio cue, but it’s very common to have the volume turned down or muted.

In this case, AVIM should use nsIAlertsService to display a toast notification appropriate to the user’s operating system. Hopefully that won’t be too distracting. A subtler way to communicate the state change would be to temporarily change the status bar text.

@1ec5
Copy link
Owner Author

1ec5 commented Nov 29, 2014

Some of AVIM’s users typically write in other languages and only pull out AVIM once in awhile. These users often disable AVIM’s toolbar button or hide it in the menu. They would be well served by a notification of some sort. As it is, they get surprised when they accidentally double-Ctrl and weird things start happening to their input.

System-standard toast notifications are too distracting; they’re huge and last too long. Instead, a doorhanger will appear for 2 seconds, pointing to the application menu, displaying the contents of the hidden toolbar button. It’ll be a bit more translucent than most doorhangers and won’t receive focus automatically.

The doorhanger may satisfy some users who want to know when AVIM is enabled but don’t want it taking up space in the toolbar. Other users, however, may have disabled the toolbar button because they really don’t want to see AVIM at all. I think this doorhanger is still useful for them, because otherwise they have no way of knowing that their Rs aren’t going to turn into hooks.

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

1 participant