Languages

Menu
Sites
Language
sensor API document (spec?) or SDK rootstrap which is correct?

Now you can see the following types of sensor in system-sensor category of wearable 2.3.2 API document (API sepc!)

SENSOR_GYROSCOPE_UNCALIBRATED 

Uncalibrated Gyroscope sensor (Since 2.3.2)

SENSOR_GEOMAGNETIC_UNCALIBRATED 

Uncalibrated Geomagnetic sensor (Since 2.3.2)

SENSOR_GYROSCOPE_ROTATION_VECTOR 

Gyroscope-based rotation vector sensor (Since 2.3.2)

SENSOR_GEOMAGNETIC_ROTATION_VECTOR 

Geomagnetic-based rotation vector sensor (Since 2.3.2)

SENSOR_HUMAN_PEDOMETER 

Pedometer (Since 2.3.2)
Privilege : http://tizen.org/privilege/healthinfo

SENSOR_HUMAN_SLEEP_MONITOR 

Sleep monitor (Since 2.3.2)
Privilege : http://tizen.org/privilege/healthinfo

SENSOR_HUMAN_SLEEP_DETECTOR 

Sleep detector (Since 2.3.2)
Privilege : http://tizen.org/privilege/healthinfo

SENSOR_HUMAN_STRESS_MONITOR 

Stress monitor (Since 2.3.2)
Privilege : http://tizen.org/privilege/healthinfo

SENSOR_LAST 

End of sensor enum values (Deprecated since 3.0)

SENSOR_CUSTOM 

Custom sensor (Deprecated since 3.0)

But there is no definition in "sensor.h" that packaged with latest SDK (tizen studio)

(tizen-studio/platforms/tizen-2.3.2/wearable/rootstraps/wearable-2.3.2-emulator.core/usr/include/sensor/sensor.h)

So I search these in platform source (https://review.tizen.org/gerrit/#/admin/projects/platform/core/api/sensor)

I found text (Since 2.3.2) is fixed to Since 3.0. but I can't know what is correct? SDK rootstrap is miss API? or spec is fail?

and I can't find any 3.0 API spec but document write it. (Deprecated since 3.0) ????? really?

 

Responses

2 Replies
Yasin Ali

Hi~,

I checked this link
https://review.tizen.org/git/?p=platform/core/api/sensor.git;a=commitdiff;h=d50a50829c20d10381334179fedb39aa1ec6e7b4

Looked in sensor.cpp file and found,

+#define WARN_DEPRECATED_SENSOR(X) \
+       do { \
+               if ((X) == SENSOR_LAST || (X) == SENSOR_CUSTOM) { \
+                       _W("DEPRECATION WARNING: This sensor type is deprecated and will be removed from next release."); \
+               } \
+       } while (0)
+

So, probably "DEPRECATION WARNING" message gives us correct direction to follow.

pius lee

NO, I can not use symbol that is not exist in header.

As you said someone want to got sensor is deprecated or not, first they must know enum value of sensor type.

But if spec don't write it, no one can try it. how to get the error from the sensor not exist?