You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Having an option between the two would be ideal, then people could use whichever method suited their situation.
What would also be great would be having a method to query whether there is a CSNotificationView on the screen at the time e.g. -(BOOL)isShowing
This way, we could check whether there's already one on the screen and not show a duplicate message.
Loving the class though - great work!
I think stacking would be the best option as a stack also is some kind of queue.
Regarding the isShowing property: It would have to be set by the presenter which animates the view on screen as the CSNotificationView itself does not have any idea whether it is at first position of the stack (=showing).
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.
The text was updated successfully, but these errors were encountered: