-
Notifications
You must be signed in to change notification settings - Fork 108
Error in conversation with Macello in Home #345
Comments
@sunjunkie please have a look. |
Yes. But let's add more detail to the issue description. The user completes the Home scenario, then the outro sequence occurs. When the outro completes, the Home scenario screen shows briefly and then the Mine Sweeper games appears. This brief appearance if the Home scenario screen should not occur at all. |
@sunjunkie is it right now? |
Remove the 1st paragraph. |
Thank you @sunjunkie |
@sunjunkie I need help on this issue? |
Please explain your problem. |
Sorry, @sunjunkie I saw your reply but I want to try more times so I can't give reply to this issue but after some more efforts, I can't understand the relation sequence between popup Event and Story sequence. |
These links provide some background- |
Ok, thank you @sunjunkie I read first one last day. I hope I get some help from 2 or 3 links. |
Hi there. So just to be clear the PopupEvents and StorySequences are unrelated. They are separate things entirely. PopupEvents are essentially just notification popups and can be triggered anywhere. StorySequences are the semi-automated dialogue sequences that can occur before and after a scene. StorySequences aren't pushed with their own view controller. They are just container in a UIView overlaying the current view controller. So, when it's finished, it is disposed of by the scene VC before the minigame VC takes over. The StorySequence class handles removing and disposing of it's own view when the sequence is finished. Resolving this issue might be as simple as not letting it do that... |
Description
The user completes the Home scenario, then the outro sequence occurs. When the outro completes, the Home scenario screen shows briefly and then the Mine Sweeper games appear. This brief appearance of the Home scenario screen should not occur at all.
Mocks
powerup.mov.zip
Acceptance Criteria
Update [Required]
or
Definition of Done
Estimation
[4] hours
The text was updated successfully, but these errors were encountered: