UI - explore improved notification UX #22388
Comments
|
In case it's not on your list of things to fix: One of the more annoying things is that there's no way to disable popups, at least for plugins. I've installed the CMake plugin to get syntax highlighting, but it complains about not having cmake installed/configured, and it pops up a notification very very frequently. Preferably all such notifications should have a "disable this notification" button. For extra fancy points, allow the user to disable just for the session, per file (?), and permanently in the user/workspace settings. |
|
To throw a concrete case on that's growing: Yes, VS Code, I know I just changed the project file. I was right here when I did it. PLEASE STOP PROMPTING ME BEFORE I'VE HAD A CHANCE TO EVEN DO ANYTHING. Holy crap that's an insanely annoying behavior. Some other plugins do the same. I absolutely want to mute some plugins outright, possibly based on verbosity level. |
|
hi @bpasero you wondered what type of warnings I was getting while using Unity. By default Unity will add a few lines to the top new .cs files, these are in basically every file. The "using" includes are not always used, so appear with green squiggle underlines. However every time you start up VSCode, it warns you about these. |
|
@HawkenKing I see, you could also report this to their extension asking for a more pleasant experience (e.g. allow to never show the warning again). |
|
We also have an issue in the C++ extension where the users stop at some library code that the debugger "knows" the source path for but the user doesn't have that source on the computer. Our users would like a way to turn off notification for these files and I think a per file/filepath or per session method would be helpful. |
|
@bpasero I would propose a subtle fade out animation when dismissing a notification. Should not distract too much but still looks a bit nicer. |
|
@levrik you mean an animation when the user explicitly clicks on the X or when the notification disappears on its own after a timeout? |
|
@bpasero I would say both. |
|
-- Sorry for the English, I used Google Translator -- @bpasero
2 - I think the notifications that need our attention could be a little transparent after the predetermined time, getting the normal color as soon as you move the mouse over it and return to the transparent if you take the mouse. 3- What maximum number of notifications? What I mean is: would it be half the VSCode window? 4- [Suggestion] Make the Windows taskbar icon blink when a background installation has finished (and we need to restart VSCode - I think that would be interesting) - this would happen when VSCode is minimized. 5- A small detail: Put the notification a little further left to follow the scroll bar line. Place the nearest notification to Status bar. So when you turn off the Status bar it will be close to the taskbar.
|
|
@Tekbr I kinda like the idea with making important notifications transparent after some time instead of letting them disappear. |
Isn't about just to have an animation. It's because UX things. |
|
@Tekbr currently the oldest notification would hide if the overall stack of notifications exceeds 600px, so it is not bound by number but rather by size (currently, we might want to change that). @Tekbr can you explain where you see a misalignment with the notification center when status bar is disabled, for me it looks OK? I can check about aligning the center to the scrollbar of the editor, though not sure that makes sense, because the notification center is floating on top of everything. @AdrianoCahete that is good reasoning, but it does not necessarily have to be the same animation that was used to show them. I find the fade-in animation quite heavy already and we might want to revisit that one (e.g. to fade an animation in from the bottom instead of from the right because the notification center is on the bottom). |
|
Yep, you can make any animation to dismiss, as long as user can clearly see that is dismissing. A small (0.3s~0.5s) timeframe animation is enough. |
|
-- Sorry for the English, I used Google Translator --
@bpasero Thanks for the info!
@bpasero Here's the picture of what I'm talking about. Remembering that it is only a detail ... If you can not leave it as it is.
|
|
-- Sorry for the English, I used Google Translator --
@bpasero For those who have the active Status Bar it is easy to see that there have been notifications. But for who deactivates? Or when we have ZenMode enabled (if using two monitors)? Even for those who leave the Status bar enabled, it would be interesting to have a contactor in the taskbar icon. Showing notification. Here are some examples that could be put (remembering that I do not know how complex this would be to implement).
|
|
@Tekbr I actually intentionally wanted to leave a gap from the status bar (or bottom window) to the notification center, but we can revisit that to make it more obvious that the center belongs to the status bar entry. Though it can also be opened when the status bar is hidden, so in that regard it is also independent from the status bar. As for feature suggestions like the task bar decorations I think we should start to separate them out into individual issues. It gets hard to track that here in the issue. Anyone feel free to file issues for individual things (both bugs or features) as you like. Make sure to not put more than one issue into a single issue 👍 I think the task bar decoration would not work unless it was clear from within the app how to dismiss the badge. And if the status bar is hidden, this would be hard. |
|
@bpasero I just would like to mention that the name of the source is overlapped by the buttons which does not look very nice (at least in my case):
Maybe you could use dots for very long source names with (
But all in all I really like the new notification concept. |
Or just move the "source name" to a line below, leaving the "button bar area" just for buttons. |
|
-- Sorry for the English, I used Google Translator -- @bpasero Thanks for your response! Let's wait for the opinion of some people, to be able to create new cases. I believe that after a formed opinion you can extract yourself to avoid duplicate cases.
About the border on the bottom and the direct part (next to the scroll bar). If you stay very full you can leave as is, they are small details even. Your explanation with Google Translate was not very clear. 😢 Sorry. 😊 😊 About the notification in the taskbar, since the Status bar is hidden I thought of a temporary icon above the gear. It would have the same function as the icon in the status bar. If the person has Status bar active, this icon will not even appear.
By clicking, it would show the notifications and also hide. If you have read all the notifications this icon will disappear !! And it would delete the notifications in the taskbar. And someone disables this bar, I have no idea. 😆 😆 😆 Maybe you did not show any notifications in the taskbar, only the blinking option, without the indicator numbers. Any other ideas? |
|
@Tekbr I really like the look/idea of having the notification center icon/badge in the activity bar rather than the status bar. |
-- Sorry for the English, I used Google Translator -- Or put this option to show / hide the rest of the text by scrolling the buttons.
|
-- Sorry for the English, I used Google Translator -- @eamodio I think the current position is more intuitive, since the notifications appear that position. That is, you would not have to move the mouse many times. Everything is very close. I'm glad you enjoyed it, but vote for this option as a secondary if Status bar is disabled. But I believe it is possible to have a choice. @bpasero Do you think it's possible? |
|
Would the 'bell' icon not be more suitable for notifications instead of the megaphone? In my mind, it seems to denote 'feedback' (Uservoice might have spoilt it for me 😉) |
|
Thanks for all the feedback on the notifications UX. We really appreciate all your suggestions and the time you have taken to help us make this a better experience. I'll respond to the recent comments and issues here, but as @bpasero has suggested, we'd really appreciate it if you could create new issues for any new suggestions you have or anything else that comes up so that we can track them more easily. Animating when closing a notification: I don't think this is necessary. We don't animate anything else out of view when closing it. Clicking the close icon and having the thing you click on disappear is sufficient feedback I believe. The reason we animate it in is because the user didn't take an explicit action to make the notification appear. So we have to do something to attract the users attention. But we don't when closing it because that was an explicit action by the user. Detached from the status bar: we are still working on the notification centre and will be working on additional capabilities such as adding UI to dismiss all notifications in one go. Once that UI is in place it might make the notification centre look less detached from the rest of the workbench. We could choose to position the notification centre affordance in the activity bar but I think we would want to show the notification centre next to the affordance. Thus this would possible obscure more code if the activity bar is on the left hand side as we would then show notifications on the left. But that could be an option I suppose. Regardless of where the notification centre affordance is displayed (status bar or activity bar) we have commands to show and hide the notification centre. So that allows users who want to focus on their code and not be distracted by the status or activity bar to continue to work but still be able to access the notifications. If we place the affordance on the status bar and then the user chooses to hide the status bar we would not move the notification centre affordance to the activity bar. The reason that somebody hides a piece of UI is more than likely because they don't want to be distracted by that piece of UI. So taking some of the UI that they have chosen to hide and putting it somewhere else would not be satisfactory. Thanks again for all the feedback. I'm going to close this issue now as we have explored and delivered a new notification UX but again, as @bpasero has suggested, we'd really appreciate it if you could create new issues for any new suggestions you have or anything else that comes up so that we can track each of those issues more easily. |
|
I had this on hand already. I'll try to keep it updated with any created issues (please reference this issue in your descriptions) and possibly make a few myself. List of requested notification features
List of requested notification API features
|
From VS UX Guidelines:
|
and others
Goal: to explore an improved notification experience that resolves the current notification UX problems
Plan of action
The text was updated successfully, but these errors were encountered: