diff --git a/TODO b/TODO index 440d3a07a..128e367dc 100644 --- a/TODO +++ b/TODO @@ -21,4 +21,7 @@ WIP: * add ::reach and rev iterators to proxy objects for faster and unsafe iterations * add example: 64 bit ids with 32 bits reserved for users' purposes * composable views and "faster views", deprecate non-owning groups -* offset instead of pages in the sparse set? top level mask for sparse sets? \ No newline at end of file +* offset instead of pages in the sparse set? top level mask for sparse sets? +* add meta dynamic cast (search base for T in parent, we have the meta type already) +* make meta base/conv node work with storage/any +* deprecate/remove meta_base, meta_conv, ... \ No newline at end of file diff --git a/docs/md/faq.md b/docs/md/faq.md index 31c39c495..8cab7aaf8 100644 --- a/docs/md/faq.md +++ b/docs/md/faq.md @@ -13,6 +13,7 @@ * [Warning C4307: integral constant overflow](#warning-C4307-integral-constant-overflow) * [Warning C4003: the min, the max and the macro](#warning-C4003-the-min-the-max-and-the-macro) * [The standard and the non-copyable types](#the-standard-and-the-non-copyable-types) + * [Which functions trigger which signals](#which-functions-trigger-which-signals) @@ -194,3 +195,24 @@ struct type { ``` Unfortunately, this will also disable aggregate initialization. + +## Which functions trigger which signals + +The `registry` class offers three signals that are emitted following specific +operations. Maybe not everyone knows what these operations are, though.
+If this isn't clear, below you can find a _vademecum_ for this purpose: + +* `on_created` is invoked when a component is first added (neither modified nor + replaced) to an entity. +* `on_update` is called whenever an existing component is modified or replaced. +* `on_destroyed` is called when a component is explicitly or implicitly removed + from an entity. + +Among the most controversial functions can be found `emplace_or_replace` and +`destroy`. However, following the above rules, it's quite simple to know what +will happen.
+In the first case, `on_created` is invoked if the entity has not the component, +otherwise the latter is replaced and therefore `on_update` is triggered. As for +the second case, components are removed from their entities and thus freed when +they are recycled. It means that `on_destroyed` is triggered for every component +owned by the entity that is destroyed. \ No newline at end of file