X-Git-Url: http://review.tizen.org/git/?p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git;a=blobdiff_plain;f=docs%2Fcontent%2Fshared-javascript-and-cpp-documentation%2Fcreating-custom-controls.md;h=946b4f07edbf5ea86fa2d371b7b824ab2917f7cc;hp=741097859e88fe03b701099f52ebaffe3e2012b8;hb=acbf7e2c17c1578c7125fa07c7eaabe1fe214406;hpb=78d6c4118411aa10112953fe6844eb08c944dd59 diff --git a/docs/content/shared-javascript-and-cpp-documentation/creating-custom-controls.md b/docs/content/shared-javascript-and-cpp-documentation/creating-custom-controls.md index 7410978..946b4f0 100644 --- a/docs/content/shared-javascript-and-cpp-documentation/creating-custom-controls.md +++ b/docs/content/shared-javascript-and-cpp-documentation/creating-custom-controls.md @@ -137,7 +137,6 @@ Dali::Toolkit::Internal::Control provides several behaviours which are specified | Behaviour | Description | |--------------------------------------|-------------------------------------------------------------------------| | ACTOR_BEHAVIOUR_NONE | No behaviour required. | -| REQUIRES_TOUCH_EVENTS | If our control requires [touch events](@ref creating-controls-events). | | REQUIRES_HOVER_EVENTS | If our control requires [hover events](@ref creating-controls-events). | | REQUIRES_WHEEL_EVENTS | If our control requires [wheel events](@ref creating-controls-events). | | REQUIRES_STYLE_CHANGE_SIGNALS | True if need to monitor style change signals such as Theme/Font change. | @@ -146,25 +145,11 @@ ________________________________________________________________________________ ### Touch, Hover & Wheel Events {#creating-controls-events} -+ A **touch event** is when any touch occurs within the bounds of the custom actor. ++ A **touch** is when any touch occurs within the bounds of the custom actor. Connect to Dali::Actor::TouchSignal(). + A **hover event** is when a pointer moves within the bounds of a custom actor (e.g. mouse pointer or hover pointer). + A **wheel event** is when the mouse wheel (or similar) is moved while hovering over an actor (via a mouse pointer or hover pointer). -If the control should needs to utilise these events, then the correct behaviour flag should be used when constructing the control. - -Then the appropriate method should be overridden. -~~~{.cpp} -// C++ -bool MyUIControlImpl::OnTouchEvent( const TouchEvent& event ) -{ - bool consumed = false; - - // Handle touch event - - // Return true if handled/consumed, false otherwise - return consumed; -} -~~~ +If the control needs to utilise hover and wheel events, then the correct behaviour flag should be used when constructing the control and then the appropriate method should be overridden. ~~~{.cpp} // C++ bool MyUIControlImpl::OnHoverEvent( const HoverEvent& event )