search

wanderingstan / zataangstuff

Automatically exported from code.google.com/p/zataangstuff
1 stars 1 forks source link

OS 2.2 Apple Feature - Press home to snap to first home screen. #66

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Press Home key 

What is the expected output? What do you see instead?

Expect: Quickgold window

See: snap back to 1st home screen.

What version of the product are you using? On what operating system?

Problem *will* manifest itself on iPhone OS 2.2 with the new feature of 
snapping back to "main" 
home screen when the home button is pressed on spring board.

Please provide any additional information below.

Obviously the developer probably already knows about this potential issue - can 
anyone 
comment (that has updated to 2.2) if its possible to disable this feature? 

Don't tell me Quickgold will die with OS 2.2 .... There's gotta be some Plist 
setting to disable the 
new feature to retain QG's usefulness.

Original issue reported on code.google.com by firas.mo...@gmail.com on 22 Nov 2008 at 8:47

GoogleCodeExporter commented 8 years ago 
QG will not get disabled because of this new feature. In fact, I am going to 
make it
work so that BOTH things happen (springboard gets snapped back and quickgold 
gets
activated) at the same time when you press the home button. 

As soon as the 2.2 jailbreak arrives, i will release the new version of 
quickgold.

Original comment by zataang...@gmail.com on 22 Nov 2008 at 8:50

GoogleCodeExporter commented 8 years ago 
ooooh!!! fancy!

That's actually a good idea... if for some reason people don't like  hiding 
every single app from SB and just use 
QG, they can use both features.

Ahh...now I can upgrade in peace...

Original comment by firas.mo...@gmail.com on 22 Nov 2008 at 9:01

GoogleCodeExporter commented 8 years ago 
2.2 jailbreak is out... what about new quickgold version? ;)))

Great idea, zataang, both things happening is a good idea!

Original comment by atm...@gmail.com on 23 Nov 2008 at 1:24

GoogleCodeExporter commented 8 years ago 
I'm not sure if it's related to the new Home Screen feature, but QuickGold 
stops responding after a while on 2.2. 
It still launches, and I can still click on the most recent icons, but I cannot 
type anything because it seems like 
the search box is not selected (and I cannot select it). 

Respringing fixes the issue. Let me know if you want more info, but I cannot 
pinpoint the exact cause of this. 
Just happens after a while of use.

Original comment by egor...@gmail.com on 23 Nov 2008 at 5:18

GoogleCodeExporter commented 8 years ago 
I can confirm the above bug. You're not able to type anything in the box 
occasionaly.

Also, QG currently does snap back to first home screen and open the QG 
interface but sometimes maybe 
one out of 10, pressing the home button only snaps back and doesn't launch QG.

Original comment by firas.mo...@gmail.com on 23 Nov 2008 at 7:36

GoogleCodeExporter commented 8 years ago 
Pretty strange. Guys, can you please inform me about updates about this bug on 
the
QuickGold list? More people can know what's going on that way... Also, if you 
can
find any more details (like precise steps to reproduce the bug) about this, 
please
let me know.

Original comment by zataang...@gmail.com on 23 Nov 2008 at 10:04

GoogleCodeExporter commented 8 years ago 
@atmb82: darn, i really did not expect it would be out so soon ;)

Original comment by zataang...@gmail.com on 23 Nov 2008 at 10:17

GoogleCodeExporter commented 8 years ago 
I can confirm comments #4 and #5 above. 

A respring get's things back to normal but when I let my phone sleep, screen 
turns off or momentarily press the 
power button to turn off the screen, then press the power or home button to 
wake up the screen the bug 
reappears. I can press the KB, launch apps in the recent list but the blinking 
cursor does not appear on the list 
box and KB presses does not register..

Original comment by fuel...@gmail.com on 24 Nov 2008 at 3:21

GoogleCodeExporter commented 8 years ago 
The steps in this Issue ticket reproduce it for me: 
http://code.google.com/p/zataangstuff/issues/detail?id=67

Original comment by egor...@gmail.com on 26 Nov 2008 at 8:52

GoogleCodeExporter commented 8 years ago 
As I stated in the other bug report (issue #67), this issue has been fixed in 
the
development version. An update will be out shortly.

Original comment by zataang...@gmail.com on 27 Nov 2008 at 11:06