X-Git-Url: http://review.tizen.org/git/?p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git;a=blobdiff_plain;f=docs%2Fcontent%2Fprogramming-guide%2Fproperties.h;h=a1a95e970cc5e961d88d6a5cec87b43e4681ae90;hp=5e5dbd0347b1cfcbe67d249c918597110b84641a;hb=74c8fd064793430f586e7f2572e3a0bd0fb50af4;hpb=53faacaf9bc394044776677e5a4d9f14dd35e05a diff --git a/docs/content/programming-guide/properties.h b/docs/content/programming-guide/properties.h index 5e5dbd0..a1a95e9 100644 --- a/docs/content/programming-guide/properties.h +++ b/docs/content/programming-guide/properties.h @@ -89,15 +89,16 @@ Macros are used to define properties for the following reasons: Two different macros are provided depending on whether the property is to be an event-side only property or an animatable property. -There are two stages: +There are three stages: -- Define the properties as an enum in the public-api header file, along with a definition of the property ranges. +- Define the property ranges as an enum in the public-api header file. There are two ranges, one for event-side only properties, and one for animatable properties. Each range should follow on from the range defined in the parent class. +- Define the properties as an enum in the public-api header file - Define the property details using the pre-defined macros to perform the type-registering of the properties. This is done for signals and actions also. Example: ImageView Source file: image-view.h: -Note that the “PropertyRange” contents “PROPERTY_START_INDEX” & "ANIMATABLE_PROPERTY_REGISTRATION_START_INDEX" are also used by the macro for order checking. + Note that the “PropertyRange” contents “PROPERTY_START_INDEX” & "ANIMATABLE_PROPERTY_REGISTRATION_START_INDEX" are also used by the macro for order checking, so should always have these names. @code /**