saru2020 / iphone-kirikae

Automatically exported from code.google.com/p/iphone-kirikae
1 stars 1 forks source link

Quitting some applications sends kirikae to background #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
iPhone/iPod Touch model: 2G
Firmware Version: 3.1
Brief description of the problem:

Quitting some apps send kirikae into bckground

What steps will reproduce the problem?
1. Try to quit few applications one by one
2. Kirikae will go to background at some point by itself

Please provide any additional information below.

Hope someone else will be able to also confirm this problems.

Thanks,
Mirko

Original issue reported on code.google.com by mirko%m-...@gtempaccount.com on 7 Oct 2009 at 5:53

GoogleCodeExporter commented 9 years ago
I am also experiencing this on the latest release of Kirikae. iPhone 3G[s] OS 
3.1.2. All applications other 
than Mail, Safari, and Phone send shut down Kirikae when closed from active 
tab.  

Original comment by steve.ci...@gmail.com on 25 Dec 2009 at 3:46

GoogleCodeExporter commented 9 years ago
Yes, same as previous poster, also 3gs on 3.1.2.

Original comment by RMW042@gmail.com on 4 Feb 2010 at 8:18

GoogleCodeExporter commented 9 years ago
Just to follow up, found a work around. This only occurs when animation is off. 
If
you turn animation on, it operates as it should. Maybe the bug will be fixed in 
the
next release?

Original comment by ants...@gmail.com on 10 Feb 2010 at 8:58

GoogleCodeExporter commented 9 years ago
Hey antsh86, thanks for the tip! I may be using Kirikae as my primary app 
switcher
again after this revelation!

Cheers!

Still would like it to work this way with animation off, but it's a small price 
to pay.

Original comment by steve.ci...@gmail.com on 10 Feb 2010 at 7:24

GoogleCodeExporter commented 9 years ago
yay! This is fixed on newest version! :)

Original comment by dr.aar...@gmail.com on 20 Feb 2010 at 2:25

GoogleCodeExporter commented 9 years ago
@dr.aarong:

Actually, this was fixed in the previous version (r170) as noted in the release 
notes. 

@all:

Marking this issue as fixed.

Original comment by gai...@gmail.com on 20 Feb 2010 at 4:00