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

Adobe AIR Development


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
Developer
Posts: 185
Registered: ‎04-05-2011
My Device: PlayBook
My Carrier: Bouygues Telecom

TextInput Change Event not fired on the new fuse TextInput

Hi there,


I want  to react to the text being typed in a TextInput, for example, the TextInput is a search box, and I refine the results of the search with each new letter typed.


The old qnx.ui.text.TextInput used to fire an Event.CHANGE event when text was modified, listening to this, I could detect new letters typed and relaunch the search.

 

Now with the new qnx.fuse.ui.text.TextInput from OS2, the TextInput doesn't fire an event anymore, so I had to stick with the old TextInput...

 

But then I wonder if there is another way I could listen to the text being typed, or if this is just a gap in the documentation of the fuse textInput and there is another event fired?

 

Thanks!

Julien
Web: smugrik.org Follow: @Smugrik
PlayBook apps:
OSCream
kiPass
Developer
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: TextInput Change Event not fired on the new fuse TextInput

There seems to be some little things not right about the fuse text input. You might want to submit a bug report so they can be certain to correct it.
Developer
Posts: 251
Registered: ‎11-22-2011
My Device: Blackberry Playbook
My Carrier: vodafone

Re: TextInput Change Event not fired on the new fuse TextInput

Same here. 

Also the KeyboardEvent.KEY_DOWN and KeyboardEvent.KEY_UP fire only on the return key. It works on the desktop but not on the device. 

Has anybody an idea how to detect inputs on a fuse TextInput?

Highlighted
Developer
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: TextInput Change Event not fired on the new fuse TextInput

A new 3.0 BB10 AIR SDK is suppose to be coming out "soon". You might want to wait till then to see if it has been corrected. But since we have no insight into when "soon" will be, it might we worth a bug report just to make certain it gets checked.
Developer
Posts: 251
Registered: ‎11-22-2011
My Device: Blackberry Playbook
My Carrier: vodafone

Re: TextInput Change Event not fired on the new fuse TextInput

Hi jtegen, i am currently not using the BB10 SDK because its an older Playbook-App i am using PB 2.0 SDK to add predictive keyboard support.  If its a bug i have no hope they will fix it, because i think RIM puts all manpower into BB10. I have decided only to listen to focus out event and remove the feature where i used it. It was anyway not very important.

Hopefully 3.0 will fix it.