karim14 / andors-trail

Automatically exported from code.google.com/p/andors-trail
0 stars 0 forks source link

SwiftKey 3's predictive text selection button bar appears. #318

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Have SwiftKey 3 v3.0.4.343 installed, enabled as your chosen virtual 
keyboard (also in system settings of your device) with English (US) enabled as 
your chosen language, and the option for "Hard keyboard" checked to "Disable 
autocomplete for the physical keyboard".
2. Have Andor's Trail v0.6.12a1-4 installed.
3. Extend the physical keyboard (at which time, changes occur in the 
background) and start a new game of Andor's Trail with the hero's name using 
six capital letters.

What is the expected output? What do you see instead?
Aside from the normal game screen displayed, an overlay of SwiftKey 3's 
predictive text selection bar is featured at the bottom of the screen in its 
normal appearance as when you are using the physical keyboard to input data 
into a text field.

What version of the product are you using? On what device?
Version 0.6.12a1-4 installed on a Motorola Droid 3 (model XT862) with Verizon's 
Android OS (v2.3.4) latest update of 5.7.906.XT862.Verizon.En.US.

Please provide any additional information below.
Many factors could play a role in experiencing difficulty in reproducing this 
event. The very fact that every wireless carrier contracts with device 
manufacturers to supply modified, or customized versions of the Android OS for 
each device they make available to their customers is a major hurdle in 
achieving compatibility when developing software for the Android OS platform.

This issue is reproducible on my device by following the steps above. It will 
remain as long as you consistently use the physical keyboard at the beginning 
of each following game play session. The collapsing and deactivating of the 
physical keyboard to play with the touch screen only, or starting your next 
game play session by touch screen only, will eliminate this issue from future 
occurrences.

Original issue reported on code.google.com by ctnbeh13@gmail.com on 16 Sep 2012 at 8:50