Lines Matching refs:callback

38 …use `FT_CALLBACK`, `FT_POINTER`, `FT_STATIC` or `FT_IGNORE` to select a callback field, a dynamica…
204 | `PB_LTYPE_SUBMSG_W_CB`           |0x09   |Submessage with pre-decoding callback.
228 …|0x40   |A field with dynamic storage size. Struct field contains a pointer to a callback function.
252 |`field_callback` | Function used to handle all callback fields in this message. By default `pb_def…
329 A pointer to the *arg* is passed to the callback when calling. It can be
330 used to store any information that the callback might need. Note that
332 `&data` in your main code, in the callback you can access it like this:
376 as for normal callback fields, except that they get called for any
395 | type                 | Pointer to the structure that defines the callback functions.
396 … to the variable that stores the field value (as used by the default extension callback functions.)
424 and user callback functions:
454 Constructs an output stream for writing into a memory buffer. It uses an internal callback that
472 trying to call stream callback manually. :
484 the callback used, calling pb_write again after it has failed once may
506 write them to output. This causes some constraints for callback fields,
543 callback fields. The typical reason for using callbacks is to have an
545 call your callback function, which in turn will call `pb_encode_<datatype>`
595 also for callback type fields.
704 If the submessage contains callback fields, the callback function might
727 call the stream callback directly.
846 The functions with names `pb_decode_<datatype>` are used when dealing with callback fields.
848 In that case, [pb_decode](#pb_decode) will call your callback function repeatedly,
856 For decoding strings and bytes fields, the length has already been decoded and the callback functio…
859 Finally, for decoding submessages in a callback, use [pb_decode](#pb_decode) and pass it the `SubMe…
954 length, and its callback function and state the same as the parent stream.