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

Auto dismiss messages #2732

Closed
tht13 opened this issue Feb 5, 2016 · 7 comments
Closed

Auto dismiss messages #2732

tht13 opened this issue Feb 5, 2016 · 7 comments
Assignees
Labels
api feature-request Request for new features or functionality

Comments

@tht13
Copy link
Contributor

tht13 commented Feb 5, 2016

Could you add API support to have timeout dismiss messages through the window.showInformationMessage (also warm and error message) API. Requiring the user to have to dismiss these manually can be intrusive if the message is not extremely pertinent. To avoid the user missing the message if they are using vscode at the time it appears it would be good to have a system where the message timeout does not begin until the window is in active use.

@jrieken jrieken added feature-request Request for new features or functionality api labels Feb 5, 2016
@jrieken jrieken self-assigned this Feb 5, 2016
@jrieken
Copy link
Member

jrieken commented Feb 5, 2016

Because those messages are rendered very prominent their intent is that a user must react on them. Messages that don't have those characteristics should use the setStatusBarMessage API (or the more generic status bar api)

I am leaning towards closing. @tht13 What is the scenario in which the status bar API isn't sufficient but the message API is too strong?

@tht13
Copy link
Contributor Author

tht13 commented Feb 6, 2016

The scenario I had in mind was a notification that updates for vscode are downloading (another issue I was going to write) or the notification saying no updates are available. But these could be solved by a status bar message.

@jrieken
Copy link
Member

jrieken commented Mar 7, 2016

Yes - those things should be in the status bar.

@lkytal
Copy link

lkytal commented Feb 16, 2017

I would still propose to add a API like showToast as the setStatusBarMessage is usually too humble to notice.

@chrisalexander
Copy link

Sorry to dig up something closed nearly a year ago but I agree with @lkytal here. I have an analyser which takes the current document, highlights two classes of word, and informs the user how many of each class was found. Telling the user the counts is something that a toast really does support where status bar and info message do not. The user needs to see the info in a prominent way (so status bar no good) and just needs to be informed about it without them needing to interact with it (so info message no good).

Please could the team reconsider an API which supports these two mechanisms? The status bar really is too subtle and can be quickly overwritten with something else by another extension.

@eug48
Copy link

eug48 commented Mar 5, 2017

My use-case is auto-updating an extension which is under development. Many of our users would be not-so-technical and the current UI is too subtle.. First it shows an "Update Available" message with an "Install Update" button. If the update is started it creates a status bar item with download progress, but also shows a "Downloading update" message since our users are likely to not notice the status bar. Once the download completes we show a "Success" message and would like to dismiss "Downloading update".

@jeremychone
Copy link

+1 on this requirement. The problem is that the StatusBarMessage is too subtle.

I really wish we had something to notify the user that things went well but still be action less (e.g., not requiring them press close or esc)

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

6 participants