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

Native 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
Highlighted
Developer
Posts: 93
Registered: ‎10-29-2012
My Device: Z10
My Carrier: Various

TouchEvent fired on a VisualNode that has not been touched!

Hello,

 

I am evaluating BB10 native development with C++ and Cascades. Everything looks cools so far except that the TouchEvent seems to get fired in the simulator on a control (VisualNode) that has not really been touched.

I do touch NEAR the control, but not exactly on the control. 

 

After further investigation of the TouchEvent that gets sent - I see that the event->localX() value is for example negative. this happens when I tap LEFT of the actual control. 

 

Obviously - I can create a filter and ignore events with local coordinates outside the actual sender's bounds, but why am I receiving these events in the first place?

 

I must be missing something obvious - I don't believe that this is default behaviour. 

 

Thanks for any insights.