Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Developer
bleucalme
Posts: 22
Registered: ‎10-30-2008
My Device: Not Specified

More VirtualKeyboard bugs..

Hi, here are 2 more bugs about the VirtualKeyboard.

 

BUG #1)

In portrait, the symbol keys are not sent to keyChar/keyDown/keyUp when we are not using the textfields.

 

BUG #2)

In portrait, keys "*" and "#" have keyDown but no keyUp (I'm not using your textfields).

 

I hope that someone from RIM will repy to my posts one day!

 

 

Please use plain text.
Administrator
MSohm
Posts: 14,229
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook
My Carrier: Bell

Re: More VirtualKeyboard bugs..

What version of BlackBerry handheld software are you testing on?  You can find this under Options, About on the BlackBerry Storm.  Are you testing on an actual BlackBerry device or the BlackBerry Simulator?

 

Have you created a MIDlet or BlackBerry CLDC application?  Where are your keyChar methods located, at the application level, screen level, manager level or field level?  From what class are you overriding these methods?

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
bleucalme
Posts: 22
Registered: ‎10-30-2008
My Device: Not Specified

Re: More VirtualKeyboard bugs..

Hi,

 

I am testing it under the BlackBerry Simulator using a Blackberry CLDC application.

 

I don't use the keychar() because I need both pressed and released events. I'm not using text fields.

 

I am using KeyUp() and KeyDown() from a class that extends Fullscreen.

 

Here's a small test application that shows the bug on the emulator.


import net.rim.device.api.ui.*; import net.rim.device.api.ui.component.*; import net.rim.device.api.ui.container.*; import net.rim.device.api.system.*; import net.rim.device.api.ui.Keypad; class KeyCheckerRIMCanvas extends FullScreen { RichTextField mheader = new RichTextField("Press END to exit."); RichTextField mLastKeyDown = new RichTextField("Last KeyDown"); RichTextField mLastKeyUp = new RichTextField("Last keyUp."); RichTextField mLastKeyRepeat = new RichTextField("Last keyRepeat."); public KeyCheckerRIMCanvas() { super(); getVirtualKeyboard().setVisibility( VirtualKeyboard.SHOW_FORCE); add(mheader); add(mLastKeyDown); add(mLastKeyRepeat); add(mLastKeyUp); } public boolean keyDown(int keyCode, int time) { if (Keypad.key(keyCode) == Keypad.KEY_END) { System.exit(0); } mLastKeyDown.setText("KeyDown: " + Keypad.key(keyCode)); return true; } public boolean keyRepeat(int keyCode, int time) { mLastKeyRepeat.setText("KeyRepeat: " + Keypad.key(keyCode)); return true; } public boolean keyUp(int keyCode, int time) { mLastKeyUp.setText("KeyUp: " + Keypad.key(keyCode)); return true; } } class KeyCheckerRIM extends net.rim.device.api.ui.UiApplication { public static void main(String[] args) { KeyCheckerRIM instance = new KeyCheckerRIM(); instance.enterEventDispatcher(); } public KeyCheckerRIM() { pushScreen(new KeyCheckerRIMCanvas()); } }

 

 


 

 

 

 

 

Please use plain text.
BlackBerry Development Advisor
twindsor
Posts: 793
Registered: ‎07-15-2008
My Device: Z10
My Carrier: Bell

Re: More VirtualKeyboard bugs..

This issue has been reproduced and logged to be fixed.

 

Have you tried using the KeyListener interface to see if that works at all?

Tim Windsor
Application Development Advisor II
Please use plain text.
Developer
dhanashreerao
Posts: 51
Registered: ‎08-25-2008
My Device: Not Specified

Re: More VirtualKeyboard bugs..

Hi,

I am using storm 4.7.0 simulator. I took 3 Numeric EditFields. One Non Editable and others Editable. When I click on Non Editable field, disappearing numbersVirtual Keyboard appears like below.

 

           4

5     6   9

       2

       0

abc|sym| <- |Enter 

 

So can not directly use rest of the missing numbers. Once clicking on editable field and adding some number, whole keyboard comes.

Please use plain text.