* functions acting on it also work for button objects.
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* @li "clicked": the user clicked the button (press/release).
* @li "repeated": the user pressed the button without releasing it.
* @li "pressed": button was pressed.
* functions acting on it also work for calendar objects.
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* - @c "changed" - emitted when the date in the calendar is changed.
* - @c "display,changed" - emitted when the current month displayed in the
* calendar is changed.
* functions acting on it also work for check objects.
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* - @c "changed" - This is called whenever the user changes the state of
* the check objects (@p event_info is always @c NULL).
* - @c "focused" - When the check has received focus. (since 1.8)
* functions acting on it also work for check objects.
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* - @c "changed" - When the color value changes on selector
* event_info is NULL.
* - @c "color,item,selected" - When user clicks on color item. The
* Get enable status of context menu disabled.
*
* @see elm_config_context_menu_disabled_set()
+ *
+ * @return @c EINA_TRUE if context menu is disabled, otherwise @c EINA_FALSE.
+ *
* @ingroup Elm_Entry
* @since 1.17
*/
* functions acting on it also work for conformant objects.
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* @li "virtualkeypad,state,on": if virtualkeypad state is switched to "on".
* (since 1.8)
* @li "virtualkeypad,state,off": if virtualkeypad state is switched to "off".
* @section entry-signals Emitted signals
*
* This widget emits the following signals, besides the ones sent from
- * @ref Elm_Layout:
+ * @ref Elm_Layout :
* @li "aborted": The escape key was pressed on a single line entry. (since 1.7)
* @li "activated": The enter key was pressed on a single line entry.
* @li "anchor,clicked": An anchor has been clicked. The event_info
*
* @ingroup Elm_Entry
*
+ * @param[in] obj The entry object
* @param[in] file The path to the file to load and save
* @param[in] format The file format
*
*
* @ingroup Elm_Entry
*
+ * @param[in] obj The entry object
* @param[out] file The path to the file to load and save
* @param[out] format The file format
*
* table by specifying the row and column where the object should be
* added, and any column or row span, if necessary.
*
- * Again, we could have this design by adding a @ref table widget to a
+ * Again, we could have this design by adding a @ref Elm_Table widget to a
* @c SWALLOW part, using elm_layout_content_set(). The same
* difference happens here when choosing to use the layout table (a
- * @c TABLE part) instead of the @ref table in a @c SWALLOW part. It's
+ * @c TABLE part) instead of the @ref Elm_Table in a @c SWALLOW part. It's
* just a matter of convenience.
*
* The layout table can be used through the @c elm_layout_table_* set of