Lines Matching full:with
24 - start with *lv*
27 - closed with the subject: *name*, *size*, *state* etc.
33 - always end ``typedef struct`` and ``typedef enum`` type names with
131 1. clarity (the ease with which other programmers can understand your intention),
132 2. readability (the ease with which other programmers can read your comments),
149 comments begin with a leading ``/**``. It ignores comments that do not have exactly
152 The following is an illustration of an API function prototype with documentation
158 * Set alignment of Widgets placed in containers with LV_STYLE_FLEX_FLOW style.
184 - Always start Doxygen comment with a brief description of the code element it documents.
191 - Describe function parameters with the ``@param`` command. When a function writes
198 - Describe return values with the ``@return`` command.
204 documentation (when it exists) with or without the single back-quotes.
217 - Place example code in a code block by surrounding it with ``@code{.c}`` and ``@endcode`` commands.
251 starts a paragraph where a note can be entered. The note ends with a blank line,
268 export them with :cpp:expr:`LV_EXPORT_CONST_INT(defined_value)` right after the ``define``.
272 - Widget members function must start with ``lv_<widget_name>`` and should receive :cpp:expr:`lv_obj…
277 - Functions and ``struct``\ s which are not part of the public API must begin with underscore in or…
280 …structure in ``lv_global.h`` and mark the variable with :cpp:expr:`(LV_GLOBAL_DEFAULT()->variable)…
304 * NULL to refresh with current text.
309 if(label == NULL) return; /* No bracket only if command is inline with if statement */
339 - in the ``.c`` file: the ``#include`` that includes the header with the closest
360 with:
385 If you want to skip any particular hook you can do so with: