I've got a view controller in my app that calculates some statistics. It does its job in the background, when it recieves certain NSNotifications. When NSNotification is received, it lays DejalBezelActivityView over its view, and when the job is done, dismisses it. So that's how it normally looks like:
I've got another controller (in the same UITabBarController) which can broadcast notifications when user adds an item to the database. The user can do that by filling data in modal view controller, which is basically a simple table view wich text fields.
The problem appears when the user hasn't dismissed the keyboard when filling the information. Modal view controller dismisses, presenting view controller sends NSNotification, and statistics view controller starts to calculate things. This is the moment when DejalBezelActivityView appears on top of unwanted view, although it shouldn't appear at all.
Interesting thing is, if the user dismisses the keyboard first and THEN presses "Save", this will not happen.
I've got a view controller in my app that calculates some statistics. It does its job in the background, when it recieves certain NSNotifications. When NSNotification is received, it lays DejalBezelActivityView over its view, and when the job is done, dismisses it. So that's how it normally looks like:
I've got another controller (in the same UITabBarController) which can broadcast notifications when user adds an item to the database. The user can do that by filling data in modal view controller, which is basically a simple table view wich text fields.
The problem appears when the user hasn't dismissed the keyboard when filling the information. Modal view controller dismisses, presenting view controller sends NSNotification, and statistics view controller starts to calculate things. This is the moment when DejalBezelActivityView appears on top of unwanted view, although it shouldn't appear at all.
Interesting thing is, if the user dismisses the keyboard first and THEN presses "Save", this will not happen.