Closed krasnyk closed 13 years ago
you're right, thanks for pointing out. In my use-cases immediateMessages weren't supposed to be sent that frequently one after another. will fix that soon.
Fixed with Commit 85f77a5650bd867e0f8090f1005e3f4bbd2325dc Immediate Messages now won't get removed from the queue if they are already in it.
Added a property canRemoveImmediateMessagesFromQueue so that you can specify whether all immediate messages stay in the queue (and therefore get displayed - kinda like 'important' messages) or whether a new posted immediate message clears all messages in the queue
Seems to be fixed in b2969135c24965a25da921ede03c84e176c842db
Download the project from http://www.DropBox.pl/file.php?name=CFD5DCF8A13CBBC0BFB344D7EE03C592 and run it with iPad simulator 4.2. As you can see in the code I'm posting following messages to the StatusBarOverlay: [[MTStatusBarOverlay sharedInstance] postImmediateMessage:@"a" animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateFinishMessage:@"finished" duration:5 animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateMessage:@"a" animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateFinishMessage:@"finished" duration:5 animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateMessage:@"a" animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateFinishMessage:@"finished" duration:5 animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateMessage:@"a" animated:YES]; [[MTStatusBarOverlay sharedInstance] postImmediateFinishMessage:@"finished" duration:5 animated:YES]; The text I see the last should be "finished", but instead of that I see "a". It does not matter how long do I wait.