nonarhero / android-bluez-ime

Automatically exported from code.google.com/p/android-bluez-ime
0 stars 0 forks source link

Dpad has odd navigation behavior #139

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
For any other issue, please delete the lines above.

What version of BluezIME are you using?
BluezIME-v1.14-Wiimote.apk  

What Android device do you have? What Android version?
Nook Color CM7 latest.

What gamepad are you using?
Wiimote

What steps will reproduce the problem?
1.DPAD Key mappings
2.Using WIIMote's DPAD
3.

What is the expected output? What do you see instead?
It should allow me to navigate through files in video players/picture viewers 
such as quickpic or mx video player; like when I'm using a keyboard. It sorta 
allows me to do so in video players (it greys out the selected file) but it 
doesn't seem to be working right as it locks out space bar function to scroll 
down for example.  

Please provide any additional information below.
I've tried various wiimote enabling ime apps but I like bluez-ime best because 
of the numerous mappings it offers.  Unfortunately it suffers from this dpad 
issue that other apps such as wiimote controller don't seem to have.   When 
working correctly navigating with the dpad should generally encompass selected 
files with a yellow border or filling.

I'd like to suggest some sort of repeat function if it isn't to hard to 
implement. It would allow you to hold down to scroll through files, which could 
be useful for navigating. The app Gamepro seems to have this feature. 

Thanks

Original issue reported on code.google.com by Rdd2k2...@gmail.com on 8 Jan 2012 at 3:52

GoogleCodeExporter commented 8 years ago
Not sure what you mean with "it locks out space bar function to scroll down" ?
Can you provide a screenshot of what it looks like, and what it is supposed to 
look like?

I have added the key repeat request as issue #140.

Original comment by kenneth@hexad.dk on 8 Jan 2012 at 9:12

GoogleCodeExporter commented 8 years ago
Quick reply, I appreciate you taking my suggestion into consideration.  

Sorry I wasn't to clear about the dpad issue. I've attached some screenshots as 
you requested, which should help clarify the problem a little.

Pictures 1&2 
Were taken while using bluez ime. Notice how either the file selected is greyed 
out or black.  In this state you are not able to use android shortcuts: Space 
to scroll down and Space+shift to scroll up (I have them mapped). You are also 
not able to use the dpad at all to navigate through pictures in quickpic.  
There's a temporary workaround that allows me to use the dpad as I desire, but 
it involves mapping dpad_down to one of the hardkeys on my nook.  Pressing the 
hardkey will turn the cursor orange and from that point I am able to navigate 
using the wii's dpad.

Pictures 3&4 
Show what should occur instead. Using a usb keyboard, simplewiicontroller or 
wiimotecontroller  all yield this result. When the orange highlight appears, 
the shorcuts mentioned above can be used.

Picture 5
I noticed that it says XP besides the dpad string.  Looking at the changelog 
for wiimotecontroller, I noticed the following: "added ALL key codes from 
android, including ones for Xperia Play games (marked XP)" I thought it may be 
related to the issue.

Shortcuts for android. They can be mapped thanks to the added meta keys.
http://www.pcworld.com/businesscenter/article/184656/android_keyboard_shortcuts_
all_the_hotkeys_you_need.html

Thanks again.

Original comment by Rdd2k2...@gmail.com on 8 Jan 2012 at 10:34

Attachments:

GoogleCodeExporter commented 8 years ago
I can reproduce it. I can use my optical trackball and move the menus and they 
get highlighted, but when I use Bluez IME, they are "greyed" instead. I have no 
idea what is causing it though. I don't think the XPeria stuff is making a 
difference, because they should be using stock Dpad messages:  
http://developer.sonyericsson.com/wp/2011/02/13/xperia-play-game-keys/

I don't have any ideas for what is causing it right now, hopefully I will think 
of something.

Original comment by kenneth@hexad.dk on 9 Jan 2012 at 8:54

GoogleCodeExporter commented 8 years ago
Oh, I just figure out what was wrong, it was a flag that was not supposed to be 
there.
Attached is a new build that has this fixed for me.
Let me know if it works for you.

Original comment by kenneth@hexad.dk on 9 Jan 2012 at 9:05

Attachments:

GoogleCodeExporter commented 8 years ago
Thanks Kenneth, that did the trick :).  I'm surprised at how quickly it took 
you to address and fix the issue; wish there were more devs like you around.  
Everything seems to be working as it should.  I hope this little change 
benefits others as well, who plan to use your app to navigate their devices 
remotely.

Original comment by Rdd2k2...@gmail.com on 9 Jan 2012 at 11:49

GoogleCodeExporter commented 8 years ago
I wish there were more devs like me too :)

Happy to hear that it works, it was a very small fix.
Thanks for the donation!

Original comment by kenneth@hexad.dk on 10 Jan 2012 at 8:23