| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
- SdkController/SdkControllerLib: move files in Apps' .../lib
- SdkController/SdkControllerSensor + MultiTouch: remove.
- SdkController/SdkControllerApp: move to upper folder,
we don't need the subfolders anymore.
Besides the removal/move of the file, there's no
code change in the app itself.
Change-Id: Ib35428d7b10fd6eb849c7ec343fe5a23bf60ed97
|
|
|
|
|
|
|
|
|
| |
Also refactor some common code from the SensorActivity
into the BaseBindingActivity.
Also rework the handler-to-UI update mechanism.
Change-Id: I0a38b16ae2b2b4adb802298793cefa51b1a73104
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SdkController Lib:
- separate new EmulatorConnection() from the actual connection.
This makes it easier to construct the object first and then
start the connection from a thread. Otherwise the
onEmulatorBindResult() callback might be called before the
main thread gets the EmulatorConnection reference.
SdkController App:
- Main activity: Display some usage help on the screen.
- Sensor handler: Fix the blocking queue used to send the
sensor events to the emulator. Also display a status
and report any connection errors.
Change-Id: Iea0f9e79256ebd5ecfef573d33efce306a0a5722
|
|
|
|
|
|
| |
This should explain what's going on.
Change-Id: I328abd139c297dad41dd8cbbdaca8e6c977e30c4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In SdkControllerLib:
- Add an "onEmulatorBindResult" callback to the emulator
listener that indicates the result of the bind operation.
This makes it easier to create the EmulatorConnection
from within a thread and capture the success/error when
it happens.
In the apps:
- Changed to use the new onEmulatorBindResult.
- Changed the app names to make them easier to indentify
in the home launcher.
- Added the missing onPause in the legacy sensors app to
close the emulator connection (otherwise trying to restart
it fails because the port is still bound by the paused
instance)
- In fact really the legacy activities should be in
singleInstance mode.
Change-Id: Ie194a75f9babebe74c899ea9327b3e4dcfe39f41
|
|
This implement sensor control using the service.
The service has a number of "handlers" (e.g.
multitouch or sensors).
The sensor handler is automatically started by the service.
The multitouch handler OTOH will just be waiting till the
controlling activity connects to it.
Change-Id: Ic5f92063916efba2c4f503d2607b58bbbe4e0ccf
|