Update notification sometimes prevents input to the rest of the app
Reported by John Y | March 13th, 2016 @ 01:17 PM
When an update notification appears and MailMate is not actively being used, it is possible for MailMate to end up in a state where it will not accept user commands until the notification is dismissed — key commands, clicks on messages, etc all result in an NSBeep and no action taken. This usually happens when the update notification appears while the machine is in Display Sleep (but the machine itself is not sleeping) with MailMate not the foreground app.
This is amplified by the fact that the update window is not shown in Exposé, nor is it shown by hovering on the dock icon when using Hyperdock. Unless the user hides every other app's windows and looks on every Space, it is impossible to find the errant notification window; the easiest resolution is to force quit MailMate (the regular quit command just produces another NSBeep) and restart it. This causes the update notification to appear at the front and be usable.
Would it be possible to have the update notification window show in Exposé, at least? That could provide a workaround as it could be brought to the front and dismissed.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.