0

I need to listen for touch events from a specific app(in blackberry 10 os). I am planning to write another app which does this. Is this possible?

APP A- the app which exists APP B- The app i am going to write

what sort of modification do i need to do for the APPA to make this possible.

someone_ smiley
  • 1,006
  • 3
  • 23
  • 42
DesirePRG
  • 6,122
  • 15
  • 69
  • 114

4 Answers4

0

I would start looking at Starting a process if you haven't all-ready.

Chad
  • 2,938
  • 3
  • 27
  • 38
0

Probably NOT !

Your app can only listen to touch events in your app and cannot spy on other apps.

nbilal
  • 1,069
  • 2
  • 10
  • 21
  • What if I Invoke another app within a thread from my app? if so would it be possible? – DesirePRG Nov 21 '13 at 06:12
  • I don't think it matters.. only one app is visible at a time and only that visible app receives the touch events. – nbilal Nov 21 '13 at 14:16
0

Not possible. This would be a major security flaw...

Ebscer
  • 27
  • 1
  • 7
  • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient [reputation](http://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](http://stackoverflow.com/help/privileges/comment). – Salvador Dali Nov 24 '13 at 02:36
  • The question asks "Is this possible?" The answer to that question is "No". – Ebscer Dec 13 '13 at 17:02
0

In the Cascades environment touch events are passed as SIGNALS which are received by SLOTS. This message passing implementation is bound to the threading model and does not have a direct inter process counterpart. Theoretically you could implement something on top of the QNX message passing system, or on top of BlackBerry Platform Services (BPS). This might be necessary if you need the kind of performance available within a single application.

The other option is to use the invokation API that BlackBerry provides in Cascades. This is a very flexible inter-process communications protocol but is inherently synchronous. Normally UI focus moves from the invoking process to the invoked process, this does not sound like what you want. The invoked process can return immediately after receiving the invokation and before posting any UI elements, but there is still the overhead of launching the invoked process, at least in the first instance, and context switching in other instances.

It might be more fruitful to be more specific about what you are really trying to accomplish.

Richard
  • 8,920
  • 2
  • 18
  • 24