Right now, when calling showInViewController:... a second time while the first view is still being presented, the new view moves over the old one - not so great.
My idea:
1: Queuing
One could create a queue as a static object of CSNotificationView which holds track of all notifications to show per view controller.
Problem: If there are many notifications stacking, the delay is too long, showing the notification might confuse the user.
2: Queuing + Stacking
Given that there won't be two or three notifications showing in the same time, one could build up a stack inspired by in Apple's Passbook: New notifications appear a bit lower than the previous one and move up when the old is dismissed.
Implementing simple user interaction allowing to kick the view out earlier (--> UIKit Dynamics) might improve UX.
Right now, when calling
showInViewController:...a second time while the first view is still being presented, the new view moves over the old one - not so great.My idea:
1: Queuing
One could create a queue as a static object of
CSNotificationViewwhich holds track of all notifications to show per view controller.Problem: If there are many notifications stacking, the delay is too long, showing the notification might confuse the user.
2: Queuing + Stacking
Given that there won't be two or three notifications showing in the same time, one could build up a stack inspired by in Apple's Passbook: New notifications appear a bit lower than the previous one and move up when the old is dismissed.
Implementing simple user interaction allowing to kick the view out earlier (--> UIKit Dynamics) might improve UX.