{"action":"created","issue":{"url":"https://api.github.com/repos/micro-manager/micro-manager/issues/343","repository_url":"https://api.github.com/repos/micro-manager/micro-manager","labels_url":"https://api.github.com/repos/micro-manager/micro-manager/issues/343/labels{/name}","comments_url":"https://api.github.com/repos/micro-manager/micro-manager/issues/343/comments","events_url":"https://api.github.com/repos/micro-manager/micro-manager/issues/343/events","html_url":"https://github.com/micro-manager/micro-manager/issues/343","id":165638282,"number":343,"title":"Processors have no mechanism to provide nice user feedback","user":{"login":"nicost","id":2153771,"avatar_url":"https://avatars.githubusercontent.com/u/2153771?v=3","gravatar_id":"","url":"https://api.github.com/users/nicost","html_url":"https://github.com/nicost","followers_url":"https://api.github.com/users/nicost/followers","following_url":"https://api.github.com/users/nicost/following{/other_user}","gists_url":"https://api.github.com/users/nicost/gists{/gist_id}","starred_url":"https://api.github.com/users/nicost/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nicost/subscriptions","organizations_url":"https://api.github.com/users/nicost/orgs","repos_url":"https://api.github.com/users/nicost/repos","events_url":"https://api.github.com/users/nicost/events{/privacy}","received_events_url":"https://api.github.com/users/nicost/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-07-14T19:22:29Z","updated_at":"2016-07-25T15:10:54Z","closed_at":null,"body":"Processing can take a long time and thing can go wrong.  Without feedback, the user is in the dark about what is going on. Processors could create their own windows for user feedback, but that seem very ugly.  It is also questionable if Processors should create blocking dialogs when something goes wrong.  Logging output is not enough as most users are not continuously checking the log.  \r\n\r\nIt would be nice to have an area where Processors can provide status updates.  That could either be the main MM window, or the On-The-Fly Processor Pipeline window.  In any case, Processors would need access to a function to provide user feedback. "},"comment":{"url":"https://api.github.com/repos/micro-manager/micro-manager/issues/comments/234982476","html_url":"https://github.com/micro-manager/micro-manager/issues/343#issuecomment-234982476","issue_url":"https://api.github.com/repos/micro-manager/micro-manager/issues/343","id":234982476,"user":{"login":"ChrisWeisiger","id":10535260,"avatar_url":"https://avatars.githubusercontent.com/u/10535260?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisWeisiger","html_url":"https://github.com/ChrisWeisiger","followers_url":"https://api.github.com/users/ChrisWeisiger/followers","following_url":"https://api.github.com/users/ChrisWeisiger/following{/other_user}","gists_url":"https://api.github.com/users/ChrisWeisiger/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisWeisiger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisWeisiger/subscriptions","organizations_url":"https://api.github.com/users/ChrisWeisiger/orgs","repos_url":"https://api.github.com/users/ChrisWeisiger/repos","events_url":"https://api.github.com/users/ChrisWeisiger/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisWeisiger/received_events","type":"User","site_admin":false},"created_at":"2016-07-25T15:10:54Z","updated_at":"2016-07-25T15:10:54Z","body":"Taking things in turn:\r\n\r\n * The alert should automatically be made visible by calling `showTextAlert`; you shouldn't need to call `setVisible` yourself. Could you please share the code you're running?\r\n\r\n * Alerts are expected to be dismissed by the user. If you mouse over them, you can either click them to dismiss them (for single-shot alerts) or a close button should show up (for multi-use alerts). This GUI may need some iteration, but it shouldn't be the code's problem to dismiss alerts in any case, unless they _want_ to dismiss the alert for some reason. For example, the alert that shows the number of images collected / remaining during an MDA automatically dismisses itself 5 seconds after the acquisition ends, if it is not dismissed earlier.\r\n\r\n * Large numbers of alerts showing up should be a relatively rare circumstance. I would expect code that wants to use alerts to usually use the mode that combines multiple lines of text into a single dialog (the version with an `owner` parameter), so you'd only get lots of alerts if you had lots of different pieces of code creating alerts. In any case they are easy to dismiss.\r\n\r\n * I'm reluctant to make the alert system try to be too clever about where on the screen it shows alerts, as well as having rules for automatically dismissing them. Alerts shouldn't be _intrusive_, just _noticeable_. Moreover, I don't want to too strongly try to anticipate how they are used or make it too easy to accidentally dismiss them. On the flipside, of course, it should not be too much work to get rid of them either, and if they're too \"well hidden\" then they don't serve any use.\r\n\r\n * I've never liked the ImageJ status line as an alert mechanism; it's too easy to miss and/or get overwritten by a later alert. However, perhaps we should consider having a specific window dedicated to alerts, so you can hide all alerts by closing the window? Or instead of closing, the window could be \"minimized\" and an icon is shown somewhere (perhaps in the main window) if there are extant alerts. "}}
{"actor":{"display_login":"ChrisWeisiger"}}