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. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Java Development

Reply
Developer
anilsisodiya
Posts: 193
Registered: ‎04-27-2009

Touch Event Field

How can we know on which field touch event generated.

Please use plain text.
Developer
rcmaniac25
Posts: 1,789
Registered: ‎04-28-2009
My Carrier: Verizon

Re: Touch Event Field

What do you mean? From an general application do you want to know which field gets the touch event or from a field do you want to know if it was touched? Or is it something different?

------------------------------------------------------------
Three simple rules:
1. Please use the search bar before making new posts.
2. Kudo posts that you find helpful.
3. If a solution has been found for your post, mark it as solved.
--I code too much. Well, too bad.
Please use plain text.
Developer
anilsisodiya
Posts: 193
Registered: ‎04-27-2009

Re: Touch Event Field


rcmaniac25 wrote:

What do you mean? From an general application do you want to know which field gets the touch event or from a field do you want to know if it was touched? Or is it something different?


 

I want to know "whether a particular field touched or not so that i can do specific action for that field "

Please use plain text.
Developer
rcmaniac25
Posts: 1,789
Registered: ‎04-28-2009
My Carrier: Verizon

Re: Touch Event Field

[ Edited ]

You override the touchEvent function in the fields you want to use.

 

You can then either change something in that field only or call some "global" function to tell it which field was touched and then do whatever global action you want.

------------------------------------------------------------
Three simple rules:
1. Please use the search bar before making new posts.
2. Kudo posts that you find helpful.
3. If a solution has been found for your post, mark it as solved.
--I code too much. Well, too bad.
Please use plain text.