diff --git a/CONTRIBUTING_8md_source.html b/CONTRIBUTING_8md_source.html new file mode 100644 index 000000000..980dcb744 --- /dev/null +++ b/CONTRIBUTING_8md_source.html @@ -0,0 +1,74 @@ + + +
+ + + + +|
+ EnTT
+ 2.7.2
+
+ |
+
+ 1.8.13
+
+
+
diff --git a/README_8md_source.html b/README_8md_source.html
index 66293663e..c4a4f94bd 100644
--- a/README_8md_source.html
+++ b/README_8md_source.html
@@ -5,7 +5,7 @@
-std::sort in a class type std::sort in a class type |
+ EnTT
+ 2.7.2
+
+ |
+
First of all, thank you very much for taking the time to contribute to the EnTT framework.
+ How to do it mostly depends on the type of contribution:
EnTT you are using (tag or commit).EnTT framework has a coverage at 100% (at least it was at 100% at the time I wrote this file) and this is the reason for which you can be confident with using it in a production environment.
+ 1.8.13
+
+
+
diff --git a/cache_8hpp_source.html b/cache_8hpp_source.html
index c6b5089c0..0c28e23d4 100644
--- a/cache_8hpp_source.html
+++ b/cache_8hpp_source.html
@@ -5,7 +5,7 @@
-Definition at line 1300 of file view.hpp.
+Definition at line 1295 of file view.hpp.
Definition at line 1414 of file view.hpp.
+Definition at line 1409 of file view.hpp.
@@ -255,7 +255,7 @@ template<typename Entity , typename Component >Definition at line 1430 of file view.hpp.
+Definition at line 1425 of file view.hpp.
@@ -289,7 +289,7 @@ template<typename Entity , typename Component >Definition at line 1398 of file view.hpp.
+Definition at line 1393 of file view.hpp.
@@ -323,7 +323,7 @@ template<typename Entity , typename Component >Definition at line 1449 of file view.hpp.
+Definition at line 1444 of file view.hpp.
@@ -357,7 +357,7 @@ template<typename Entity , typename Component >begin and end if you want to iterate the view in the expected order.Definition at line 1382 of file view.hpp.
+Definition at line 1377 of file view.hpp.
@@ -405,7 +405,7 @@ template<typename Func > -Definition at line 1524 of file view.hpp.
+Definition at line 1519 of file view.hpp.
@@ -453,7 +453,7 @@ template<typename Func > -Definition at line 1543 of file view.hpp.
+Definition at line 1538 of file view.hpp.
@@ -485,7 +485,7 @@ template<typename Entity , typename Component >Checks whether the view is empty.
Definition at line 1334 of file view.hpp.
+Definition at line 1329 of file view.hpp.
@@ -519,7 +519,7 @@ template<typename Entity , typename Component >Definition at line 1468 of file view.hpp.
+Definition at line 1463 of file view.hpp.
@@ -553,7 +553,7 @@ template<typename Entity , typename Component >Definition at line 1487 of file view.hpp.
+Definition at line 1482 of file view.hpp.
@@ -592,7 +592,7 @@ template<typename Entity , typename Component >Definition at line 1496 of file view.hpp.
+Definition at line 1491 of file view.hpp.
@@ -631,7 +631,7 @@ template<typename Entity , typename Component >Definition at line 1505 of file view.hpp.
+Definition at line 1500 of file view.hpp.
@@ -665,7 +665,7 @@ template<typename Entity , typename Component >begin and end if you want to iterate the view in the expected order.Definition at line 1350 of file view.hpp.
+Definition at line 1345 of file view.hpp.
@@ -699,7 +699,7 @@ template<typename Entity , typename Component >begin and end if you want to iterate the view in the expected order.Definition at line 1366 of file view.hpp.
+Definition at line 1361 of file view.hpp.
@@ -731,7 +731,7 @@ template<typename Entity , typename Component >Returns the number of instances of the given type.
Definition at line 1326 of file view.hpp.
+Definition at line 1321 of file view.hpp.
diff --git a/classentt_1_1Registry-members.html b/classentt_1_1Registry-members.html index 9853e4beb..a2c8cc986 100644 --- a/classentt_1_1Registry-members.html +++ b/classentt_1_1Registry-members.html @@ -5,7 +5,7 @@ -This is the complete list of members for entt::Registry< Entity >, including all inherited members.
| accommodate(const entity_type entity, Args &&... args) | entt::Registry< Entity > | inline | ||||
| assign(tag_t, const entity_type entity, Args &&... args) | entt::Registry< Entity > | inline | ||||
| assign(const entity_type entity, Args &&... args) | entt::Registry< Entity > | inline | ||||
| attachee() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| capacity() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| capacity() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| component_type typedef | entt::Registry< Entity > | |||||
| construction(tag_t) ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| construction() ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| contains() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| create() | entt::Registry< Entity > | inline | ||||
| current(const entity_type entity) const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| data() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| destroy(tag_t) | entt::Registry< Entity > | inline | ||||
| destroy(const entity_type entity) | entt::Registry< Entity > | inline | ||||
| destroy(Type...) | entt::Registry< Entity > | inline | ||||
| destruction(tag_t) ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| destruction() ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| discard() | entt::Registry< Entity > | inline | ||||
| each(Func func) const | entt::Registry< Entity > | inline | ||||
| empty() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| empty() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| alive() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| assign(tag_t, const entity_type entity, Args &&... args) | entt::Registry< Entity > | inline | ||||
| assign(const entity_type entity, Args &&... args) | entt::Registry< Entity > | inline | ||||
| attachee() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| capacity() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| capacity() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| component_type typedef | entt::Registry< Entity > | |||||
| construction(tag_t) ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| construction() ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| contains() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| create() | entt::Registry< Entity > | inline | ||||
| current(const entity_type entity) const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| data() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| destroy(tag_t) | entt::Registry< Entity > | inline | ||||
| destroy(const entity_type entity) | entt::Registry< Entity > | inline | ||||
| destroy(Type...) | entt::Registry< Entity > | inline | ||||
| destruction(tag_t) ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| destruction() ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| discard() | entt::Registry< Entity > | inline | ||||
| each(Func func) const | entt::Registry< Entity > | inline | ||||
| empty() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| empty() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| entity(const entity_type entity) const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| entity_type typedef | entt::Registry< Entity > | |||||
| fast(const entity_type entity) const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
| get() const ENTT_NOEXCEPT | entt::Registry< Entity > | inline | ||||
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
||||||
| Returns the number of existing components of the given type. More... | ||||||
| size_type | size () const ENTT_NOEXCEPT | |||||
| Returns the number of entities still in use. More... | ||||||
| Returns the number of entities created so far. More... | ||||||
| size_type | alive () const ENTT_NOEXCEPT | |||||
| Returns the number of entities still in use. More... | ||||||
| template<typename Component > | ||||||
| void | reserve (const size_type cap) | |||||
| Increases the capacity of the pool for the given component. More... | ||||||
| const entity_type * | data () const ENTT_NOEXCEPT | |||||
| Direct access to the list of entities of a given pool. More... | ||||||
| bool | valid (const entity_type entity) const ENTT_NOEXCEPT | |||||
| bool | valid (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Checks if an entity identifier refers to a valid entity. More... | ||||||
| bool | fast (const entity_type entity) const ENTT_NOEXCEPT | |||||
| bool | fast (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Checks if an entity identifier refers to a valid entity. More... | ||||||
| version_type | version (const entity_type entity) const ENTT_NOEXCEPT | |||||
| entity_type | entity (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Returns the entity identifier without the version. More... | ||||||
| version_type | version (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Returns the version stored along with an entity identifier. More... | ||||||
| version_type | current (const entity_type entity) const ENTT_NOEXCEPT | |||||
| version_type | current (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Returns the actual version for an entity identifier. More... | ||||||
| entity_type | create () | |||||
| void | destroy (tag_t) | |||||
| Destroys the entity that owns the given tag, if any. More... | ||||||
| void | destroy (const entity_type entity) | |||||
| void | destroy (const entity_type entity) | |||||
| Destroys an entity and lets the registry recycle the identifier. More... | ||||||
| template<typename... Component, typename... Type> | ||||||
| void | destroy (Type...) | |||||
| Destroys the entities that own he given components, if any. More... | ||||||
| Destroys the entities that own the given components, if any. More... | ||||||
| template<typename Tag , typename... Args> | ||||||
| Tag & | assign (tag_t, const entity_type entity, Args &&... args) | |||||
| Tag & | assign (tag_t, const entity_type entity, Args &&... args) | |||||
| Attaches the given tag to an entity. More... | ||||||
| template<typename Component , typename... Args> | ||||||
| Component & | assign (const entity_type entity, Args &&... args) | |||||
| Component & | assign (const entity_type entity, Args &&... args) | |||||
| Assigns the given component to an entity. More... | ||||||
| template<typename Tag > | ||||||
| Removes the given tag from its owner, if any. More... | ||||||
| template<typename Component > | ||||||
| void | remove (const entity_type entity) | |||||
| void | remove (const entity_type entity) | |||||
| Removes the given component from an entity. More... | ||||||
| template<typename Tag > | ||||||
| Checks if the given tag has an owner. More... | ||||||
| template<typename Tag > | ||||||
| bool | has (tag_t, const entity_type entity) const ENTT_NOEXCEPT | |||||
| bool | has (tag_t, const entity_type entity) const ENTT_NOEXCEPT | |||||
| Checks if an entity owns the given tag. More... | ||||||
| template<typename... Component> | ||||||
| bool | has (const entity_type entity) const ENTT_NOEXCEPT | |||||
| bool | has (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Checks if an entity has all the given components. More... | ||||||
| template<typename Tag > | ||||||
| Returns a reference to the given tag. More... | ||||||
| template<typename Component > | ||||||
| const Component & | get (const entity_type entity) const ENTT_NOEXCEPT | |||||
| const Component & | get (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Returns a reference to the given component for an entity. More... | ||||||
| template<typename Component > | ||||||
| Component & | get (const entity_type entity) ENTT_NOEXCEPT | |||||
| Component & | get (const entity_type entity) ENTT_NOEXCEPT | |||||
| Returns a reference to the given component for an entity. More... | ||||||
| template<typename... Component> | ||||||
| std::enable_if_t<(sizeof...(Component) > 1), std::tuple< const Component &... > > | get (const entity_type entity) const ENTT_NOEXCEPT | |||||
| std::enable_if_t<(sizeof...(Component) > 1), std::tuple< const Component &... > > | get (const entity_type entity) const ENTT_NOEXCEPT | |||||
| Returns a reference to the given components for an entity. More... | ||||||
| template<typename... Component> | ||||||
| std::enable_if_t<(sizeof...(Component) > 1), std::tuple< Component &... > > | get (const entity_type entity) ENTT_NOEXCEPT | |||||
| std::enable_if_t<(sizeof...(Component) > 1), std::tuple< Component &... > > | get (const entity_type entity) ENTT_NOEXCEPT | |||||
| Returns a reference to the given components for an entity. More... | ||||||
| template<typename Tag , typename... Args> | ||||||
| Replaces the given tag. More... | ||||||
| template<typename Component , typename... Args> | ||||||
| Component & | replace (const entity_type entity, Args &&... args) | |||||
| Component & | replace (const entity_type entity, Args &&... args) | |||||
| Replaces the given component for an entity. More... | ||||||
| template<typename Tag > | ||||||
| entity_type | move (const entity_type entity) ENTT_NOEXCEPT | |||||
| entity_type | move (const entity_type entity) ENTT_NOEXCEPT | |||||
| Changes the owner of the given tag. More... | ||||||
| template<typename Tag > | ||||||
| Gets the owner of the given tag, if any. More... | ||||||
| template<typename Component , typename... Args> | ||||||
| Component & | accommodate (const entity_type entity, Args &&... args) | |||||
| Component & | accommodate (const entity_type entity, Args &&... args) | |||||
| Assigns or replaces the given component for an entity. More... | ||||||
| template<typename Tag > | ||||||
| Sorts two pools of components in the same way. More... | ||||||
| template<typename Component > | ||||||
| void | reset (const entity_type entity) | |||||
| void | reset (const entity_type entity) | |||||
| Resets the given component for an entity. More... | ||||||
| template<typename Component > | ||||||
| void | each (Func func) const | |||||
| Iterates all the entities that are still in use. More... | ||||||
| bool | orphan (const entity_type entity) const | |||||
| bool | orphan (const entity_type entity) const | |||||
| Checks if an entity is an orphan. More... | ||||||
| template<typename Func > | ||||||
+
|
+ +inline | +
Returns the number of entities still in use.
+Definition at line 231 of file registry.hpp.
Definition at line 543 of file registry.hpp.
+Definition at line 588 of file registry.hpp.
@@ -563,7 +601,7 @@ template<typename Component , typename... Args>Definition at line 574 of file registry.hpp.
+Definition at line 619 of file registry.hpp.
@@ -605,7 +643,7 @@ template<typename Tag >Definition at line 879 of file registry.hpp.
+Definition at line 924 of file registry.hpp.
@@ -645,7 +683,7 @@ template<typename Component >Definition at line 231 of file registry.hpp.
+Definition at line 268 of file registry.hpp.
@@ -677,7 +715,7 @@ template<typename Entity>Returns the number of entities that a registry has currently allocated space for.
Definition at line 240 of file registry.hpp.
+Definition at line 277 of file registry.hpp.
@@ -723,7 +761,7 @@ template<typename Tag >Definition at line 944 of file registry.hpp.
+Definition at line 989 of file registry.hpp.
@@ -768,7 +806,7 @@ template<typename Component >Definition at line 973 of file registry.hpp.
+Definition at line 1018 of file registry.hpp.
@@ -808,7 +846,7 @@ template<typename... Component>Definition at line 1397 of file registry.hpp.
+Definition at line 1422 of file registry.hpp.
@@ -847,7 +885,7 @@ template<typename Entity>The returned entity has no components nor tags assigned.
Definition at line 402 of file registry.hpp.
+Definition at line 448 of file registry.hpp.
@@ -889,7 +927,7 @@ template<typename Entity>Definition at line 379 of file registry.hpp.
+Definition at line 425 of file registry.hpp.
@@ -931,7 +969,7 @@ template<typename Component >Definition at line 316 of file registry.hpp.
+Definition at line 353 of file registry.hpp.
@@ -973,7 +1011,7 @@ template<typename Tag > -Definition at line 438 of file registry.hpp.
+Definition at line 483 of file registry.hpp.
@@ -1016,7 +1054,7 @@ Attempting to use an invalid entity results in undefined behavior.Definition at line 464 of file registry.hpp.
+Definition at line 509 of file registry.hpp.
@@ -1048,10 +1086,10 @@ template<typename... Component, typename... Type>Destroys the entities that own he given components, if any.
+Destroys the entities that own the given components, if any.
Convenient shortcut to destroy a set of entities at once.
Syntactic sugar for the following snippet:
| Component | Types of components to use to search for the entities. | ||||||
| Type | Type of view to use or empty to use a standard view. |
+
|
+ +inline | +
Returns the entity identifier without the version.
+| entity | An entity identifier, either valid or not. |
Definition at line 395 of file registry.hpp.
Definition at line 347 of file registry.hpp.
+Definition at line 384 of file registry.hpp.
@@ -1400,7 +1477,7 @@ template<typename Tag >Definition at line 690 of file registry.hpp.
+Definition at line 735 of file registry.hpp.
@@ -1442,7 +1519,7 @@ template<typename Tag >Definition at line 708 of file registry.hpp.
+Definition at line 753 of file registry.hpp.
@@ -1491,7 +1568,7 @@ template<typename Component >Definition at line 727 of file registry.hpp.
+Definition at line 772 of file registry.hpp.
@@ -1540,7 +1617,7 @@ template<typename Component >Definition at line 748 of file registry.hpp.
+Definition at line 793 of file registry.hpp.
@@ -1589,7 +1666,7 @@ template<typename... Component>Definition at line 768 of file registry.hpp.
+Definition at line 813 of file registry.hpp.
@@ -1638,7 +1715,7 @@ template<typename... Component>Definition at line 788 of file registry.hpp.
+Definition at line 833 of file registry.hpp.
@@ -1678,7 +1755,7 @@ template<typename Tag >Definition at line 624 of file registry.hpp.
+Definition at line 669 of file registry.hpp.
@@ -1722,7 +1799,7 @@ template<typename Tag >Checks if an entity owns the given tag.
Syntactic sugar for the following snippet:
-| Tag | Type of tag for which to perform the check. |
Definition at line 651 of file registry.hpp.
+Definition at line 696 of file registry.hpp.
@@ -1785,7 +1862,7 @@ template<typename... Component>Definition at line 668 of file registry.hpp.
+Definition at line 713 of file registry.hpp.
@@ -1835,7 +1912,7 @@ template<typename Tag >Definition at line 857 of file registry.hpp.
+Definition at line 902 of file registry.hpp.
@@ -1937,7 +2014,7 @@ template<typename Entity>Definition at line 1231 of file registry.hpp.
+Definition at line 1276 of file registry.hpp.
@@ -1986,7 +2063,7 @@ template<typename Func > -Definition at line 1265 of file registry.hpp.
+Definition at line 1310 of file registry.hpp.
@@ -2028,7 +2105,7 @@ template<typename... Component> -Definition at line 1329 of file registry.hpp.
+Definition at line 1374 of file registry.hpp.
@@ -2070,7 +2147,7 @@ template<typename Component >Definition at line 278 of file registry.hpp.
+Definition at line 315 of file registry.hpp.
@@ -2112,7 +2189,7 @@ template<typename Component >Definition at line 297 of file registry.hpp.
+Definition at line 334 of file registry.hpp.
@@ -2151,7 +2228,7 @@ template<typename Tag > -Definition at line 587 of file registry.hpp.
+Definition at line 632 of file registry.hpp.
@@ -2199,7 +2276,7 @@ template<typename Component > -Definition at line 610 of file registry.hpp.
+Definition at line 655 of file registry.hpp.
@@ -2260,7 +2337,7 @@ template<typename Tag , typename... Args>Definition at line 811 of file registry.hpp.
+Definition at line 856 of file registry.hpp.
@@ -2322,7 +2399,7 @@ template<typename Component , typename... Args>Definition at line 836 of file registry.hpp.
+Definition at line 881 of file registry.hpp.
@@ -2369,7 +2446,7 @@ template<typename Component > -Definition at line 208 of file registry.hpp.
+Definition at line 245 of file registry.hpp.
@@ -2408,7 +2485,7 @@ template<typename Entity> -Definition at line 221 of file registry.hpp.
+Definition at line 258 of file registry.hpp.
@@ -2457,7 +2534,7 @@ template<typename Component > -Definition at line 1135 of file registry.hpp.
+Definition at line 1180 of file registry.hpp.
@@ -2497,7 +2574,7 @@ template<typename Component > -Definition at line 1156 of file registry.hpp.
+Definition at line 1201 of file registry.hpp.
@@ -2529,7 +2606,7 @@ template<typename Entity>Resets a whole registry.
Destroys all the entities. After a call to reset, all the entities still in use are recycled with a new version number. In case entity identifers are stored around, the valid member function can be used to know if they are still valid.
Definition at line 1176 of file registry.hpp.
+Definition at line 1221 of file registry.hpp.
@@ -2564,7 +2641,7 @@ template<typename Entity>Definition at line 1555 of file registry.hpp.
+Definition at line 1580 of file registry.hpp.
@@ -2604,7 +2681,7 @@ template<typename Component >Definition at line 186 of file registry.hpp.
+Definition at line 215 of file registry.hpp.
@@ -2633,10 +2710,10 @@ template<typename Entity>Returns the number of entities still in use.
-Returns the number of entities created so far.
+Definition at line 194 of file registry.hpp.
+Definition at line 223 of file registry.hpp.
Definition at line 1526 of file registry.hpp.
+Definition at line 1551 of file registry.hpp.
@@ -2748,7 +2825,7 @@ template<typename Component , typename Compare , typename Sort = StdSort, ty -Definition at line 1078 of file registry.hpp.
+Definition at line 1123 of file registry.hpp.
@@ -2797,7 +2874,7 @@ template<typename To , typename From > -Definition at line 1114 of file registry.hpp.
+Definition at line 1159 of file registry.hpp.
@@ -2840,7 +2917,7 @@ template<typename Tag >Definition at line 159 of file registry.hpp.
+Definition at line 188 of file registry.hpp.
@@ -2882,7 +2959,7 @@ template<typename Component >Definition at line 176 of file registry.hpp.
+Definition at line 205 of file registry.hpp.
@@ -2921,7 +2998,7 @@ template<typename Entity>Definition at line 325 of file registry.hpp.
+Definition at line 362 of file registry.hpp.
@@ -2958,9 +3035,9 @@ template<typename Entity> -Definition at line 358 of file registry.hpp.
+Definition at line 404 of file registry.hpp.
@@ -3019,7 +3096,7 @@ template<typename... Component>Definition at line 1308 of file registry.hpp.
+Definition at line 1353 of file registry.hpp.
@@ -3080,7 +3157,7 @@ template<typename... Component>Definition at line 1443 of file registry.hpp.
+Definition at line 1468 of file registry.hpp.
@@ -3134,7 +3211,7 @@ template<typename Component >Definition at line 1473 of file registry.hpp.
+Definition at line 1498 of file registry.hpp.
@@ -3206,7 +3283,7 @@ template<typename It >Definition at line 1505 of file registry.hpp.
+Definition at line 1530 of file registry.hpp.
diff --git a/classentt_1_1ResourceCache-members.html b/classentt_1_1ResourceCache-members.html index 322c21226..645183e45 100644 --- a/classentt_1_1ResourceCache-members.html +++ b/classentt_1_1ResourceCache-members.html @@ -5,7 +5,7 @@ -Definition at line 1595 of file view.hpp.
+Definition at line 1590 of file view.hpp.
Definition at line 1769 of file view.hpp.
+Definition at line 1764 of file view.hpp.
@@ -235,7 +235,7 @@ template<typename Entity >Definition at line 1787 of file view.hpp.
+Definition at line 1782 of file view.hpp.
@@ -269,7 +269,7 @@ template<typename Entity >Definition at line 1743 of file view.hpp.
+Definition at line 1738 of file view.hpp.
@@ -303,7 +303,7 @@ template<typename Entity >Definition at line 1806 of file view.hpp.
+Definition at line 1801 of file view.hpp.
@@ -342,7 +342,7 @@ template<typename Entity >Definition at line 1860 of file view.hpp.
+Definition at line 1855 of file view.hpp.
@@ -390,7 +390,7 @@ template<typename Func > -Definition at line 1882 of file view.hpp.
+Definition at line 1877 of file view.hpp.
@@ -422,7 +422,7 @@ template<typename Entity >Checks if the view is definitely empty.
Definition at line 1725 of file view.hpp.
+Definition at line 1720 of file view.hpp.
@@ -456,7 +456,7 @@ template<typename Entity >Definition at line 1832 of file view.hpp.
+Definition at line 1827 of file view.hpp.
@@ -490,7 +490,7 @@ template<typename Entity >Definition at line 1851 of file view.hpp.
+Definition at line 1846 of file view.hpp.
@@ -522,7 +522,7 @@ template<typename Entity >Estimates the number of entities that have the given components.
Definition at line 1717 of file view.hpp.
+Definition at line 1712 of file view.hpp.
diff --git a/classentt_1_1Scheduler-members.html b/classentt_1_1Scheduler-members.html index 3a91079bb..47b8bf888 100644 --- a/classentt_1_1Scheduler-members.html +++ b/classentt_1_1Scheduler-members.html @@ -5,7 +5,7 @@ -

diff --git a/classentt_1_1Sink.html b/classentt_1_1Sink.html
index 19a546db3..d95cb426e 100644
--- a/classentt_1_1Sink.html
+++ b/classentt_1_1Sink.html
@@ -5,7 +5,7 @@
-
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
hashed_string.hpp
- 111 constexpr entt::HashedString operator"" ENTT_HS_SUFFIX(const char *str, std::size_t) ENTT_NOEXCEPT { constexpr bool operator!=(const HashedString &lhs, const HashedString &rhs) ENTT_NOEXCEPT Compares two hashed strings. Definition: hashed_string.hpp:103 116 constexpr entt::HashedString operator"" ENTT_HS_SUFFIX(const char *str, std::size_t) ENTT_NOEXCEPT { constexpr bool operator!=(const HashedString &lhs, const HashedString &rhs) ENTT_NOEXCEPT Compares two hashed strings. Definition: hashed_string.hpp:103 constexpr HashedString(ConstCharWrapper wrapper) ENTT_NOEXCEPT Explicit constructor on purpose to avoid constructing a hashed string directly from a const char *... Definition: hashed_string.hpp:66 constexpr bool operator==(const HashedString &other) const ENTT_NOEXCEPT Compares two hashed strings. Definition: hashed_string.hpp:87
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
helper.hpp
- 30 accumulator_type accumulator = { ((registry.template has<Component>(entity) ? void() : (registry.template assign<Component>(entity), void())), 0)... };
+ 32 accumulator_type accumulator = { ((registry.template has<Component>(entity) ? void() : (registry.template assign<Component>(entity), void())), 0)... };
-void dependency(Registry< Entity > ®istry, const Entity entity) Dependency function prototype. Definition: helper.hpp:28 void dependency(Registry< Entity > ®istry, const Entity entity) Dependency function prototype. Definition: helper.hpp:30 std::integral_constant< typename HashedString::hash_type, Value > label Alias template to ease the assignment of labels to entities. Definition: helper.hpp:99 diff --git a/hierarchy.html b/hierarchy.html index b554a1728..4247bfb3d 100644 --- a/hierarchy.html +++ b/hierarchy.html @@ -5,7 +5,7 @@ -
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
▼CInvoker |
| Centt::SigH< Ret(Args...), Collector > | Unmanaged signal handler definition | Centt::Monostate< hash_type > | Minimal implementation of the monostate pattern | Centt::persistent_t | Persistent view type used to disambiguate overloads | Centt::PersistentView< Entity, Component > | Persistent view | Centt::Process< Derived, Delta > | Base class for processes | ▼Centt::Process< ProcessAdaptor< Func, Delta >, Delta > | Centt::ProcessAdaptor< Func, Delta > | Adaptor for lambdas and functors to turn them into processes | Centt::Prototype< Entity > | Prototype container for concepts | Centt::raw_t | Raw view type used to disambiguate overloads | Centt::RawView< Entity, Component > | Raw view | Centt::Registry< Entity > | Fast and reliable entity-component system | Centt::ResourceCache< Resource > | Simple cache for resources of a given type | Centt::ResourceHandle< Resource > | Shared resource handle | Centt::ResourceLoader< Loader, Resource > | Base class for resource loaders | Centt::RuntimeView< Entity > | Runtime view | Centt::Scheduler< Delta > | Cooperative scheduler for processes | Centt::ServiceLocator< Service > | Service locator, nothing more | Centt::SigH< Function, Collector > | Unmanaged signal handler declaration | Centt::SigH< void(const Event &)> | Centt::Sink< Function > | Sink implementation | Centt::Sink< Ret(Args...)> | Sink implementation | Centt::Snapshot< Entity > | Utility class to create snapshots from a registry | Centt::SnapshotLoader< Entity > | Utility class to restore a snapshot as a whole | Centt::SparseSet<... > | Sparse set | ▼Centt::SparseSet< Entity > | Basic sparse set implementation | Centt::SparseSet< Entity, Type > | Extended sparse set implementation | Centt::StdSort | Function object to wrap | std::sort in a class type Centt::tag_t | Tag class type used to disambiguate overloads | Centt::View< Entity, Component > | Multi component view | Centt::View< Entity, Component > | Single component view specialization | Centt::OneShotBubbleSort | Function object for performing bubble sort (single iteration) | Centt::persistent_t | Persistent view type used to disambiguate overloads | Centt::PersistentView< Entity, Component > | Persistent view | Centt::Process< Derived, Delta > | Base class for processes | ▼Centt::Process< ProcessAdaptor< Func, Delta >, Delta > | Centt::ProcessAdaptor< Func, Delta > | Adaptor for lambdas and functors to turn them into processes | Centt::Prototype< Entity > | Prototype container for concepts | Centt::raw_t | Raw view type used to disambiguate overloads | Centt::RawView< Entity, Component > | Raw view | Centt::Registry< Entity > | Fast and reliable entity-component system | Centt::ResourceCache< Resource > | Simple cache for resources of a given type | Centt::ResourceHandle< Resource > | Shared resource handle | Centt::ResourceLoader< Loader, Resource > | Base class for resource loaders | Centt::RuntimeView< Entity > | Runtime view | Centt::Scheduler< Delta > | Cooperative scheduler for processes | Centt::ServiceLocator< Service > | Service locator, nothing more | Centt::SigH< Function, Collector > | Unmanaged signal handler declaration | Centt::SigH< void(const Event &)> | Centt::Sink< Function > | Sink implementation | Centt::Sink< Ret(Args...)> | Sink implementation | Centt::Snapshot< Entity > | Utility class to create snapshots from a registry | Centt::SnapshotLoader< Entity > | Utility class to restore a snapshot as a whole | Centt::SparseSet<... > | Sparse set | ▼Centt::SparseSet< Entity > | Basic sparse set implementation | Centt::SparseSet< Entity, Type > | Extended sparse set implementation | Centt::StdSort | Function object to wrap | std::sort in a class type Centt::tag_t | Tag class type used to disambiguate overloads | Centt::View< Entity, Component > | Multi component view | Centt::View< Entity, Component > | Single component view specialization | | |||||
+EnTT is a header-only, tiny and easy to use framework written in modern C++.
- It was originally designed entirely around an architectural pattern called ECS that is used mostly in game development. For further details:
EnTT is a header-only, tiny and easy to use entity-component system (and much more) written in modern C++.
+ The entity-component-system (also known as ECS) is an architectural pattern used mostly in game development. For further details:
A long time ago, the sole entity-component system was part of the project. After a while the codebase has grown and more and more classes have become part of the repository.
- That's why today it's called the EnTT Framework.
Currently, EnTT is tested on Linux, Microsoft Windows and OS X. It has proven to work also on both Android and iOS.
- Most likely it will not be problematic on other systems as well, but has not been sufficiently tested so far.
EnTT was written initially as a faster alternative to other well known and open source entity-component systems. Nowadays the EnTT framework is moving its first steps. Much more will come in the future and hopefully I'm going to work on it for a long time.
- Requests for feature, PR, suggestions ad feedback are highly appreciated.
If you find you can help me and want to contribute to the EnTT framework with your experience or you do want to get part of the project for some other reasons, feel free to contact me directly (you can find the mail in the profile).
- I can't promise that each and every contribution will be accepted, but I can assure that I'll do my best to take them all seriously.
Here is a brief list of what it offers today:
+ Here is a brief, yet incomplete list of what it offers today:Consider it a work in progress. For more details and an updated list, please refer to the online documentation. It probably contains much more. Moreover, the whole API is fully documented in-code for those who are brave enough to read it.
- Continue reading to know how the different parts of the project work or follow the link above to take a look at the API reference.
Consider it a work in progress. The whole API is also fully documented in-code for those who are brave enough to read it.
+Currently, EnTT is tested on Linux, Microsoft Windows and OS X. It has proven to work also on both Android and iOS.
+ Most likely it will not be problematic on other systems as well, but has not been sufficiently tested so far.
I started working on EnTT because of the wrong reason: my goal was to design an entity-component system that beated another well known open source solution in terms of performance and used (possibly) less memory in the average case.
In the end, I did it, but it wasn't much satisfying. Actually it wasn't satisfying at all. The fastest and nothing more, fairly little indeed. When I realized it, I tried hard to keep intact the great performance of EnTT and to add all the features I wanted to see in my own library at the same time.
Today EnTT is finally what I was looking for: still faster than its competitors, lower memory usage in the average case, a really good API and an amazing set of features. And even more, of course.
Nowadays, EnTT is finally what I was looking for: still faster than its competitors, lower memory usage in the average case, a really good API and an amazing set of features. And even more, of course.
As it stands right now, EnTT is just fast enough for my requirements if compared to my first choice (it was already amazingly fast actually).
Below is a comparison between the two (both of them compiled with GCC 7.3.0 on a Dell XPS 13 out of the mid 2014):
EnTT, choose it because of its API, features and performance, not because there is a benchmark somewhere that makes it seem the fastest.
Probably I'll try to get out of EnTT more features and even better performance in the future, mainly for fun.
If you want to contribute and/or have any suggestion, feel free to make a PR or open an issue to discuss your idea.
To be able to use EnTT, users must provide a full-featured compiler that supports at least C++14.
The requirements below are mandatory to compile the tests and to extract the documentation:
EnTT is a header-only library. This means that including the entt.hpp header is enough to include the whole framework and use it. For those who are interested only in the entity-component system, consider to include the sole entity/registry.hpp header instead.
+
EnTT is a header-only library. This means that including the entt.hpp header is enough to include the library as a whole and use it. For those who are interested only in the entity-component system, consider to include the sole entity/registry.hpp header instead.
It's a matter of adding the following line to the top of a file:
Use the line below to include only the entity-component system instead:
Then pass the proper -I argument to the compiler to add the src directory to the include paths.
To make sure that an application and a shared library that use both EnTT can interact correctly when symbols are hidden by default, there are some tricks to follow.
+ In particular and in order to avoid undefined behaviors, all the instantiation of the Family class template shall be made explicit along with the system-wide specifier to use to export them.
At the time I'm writing this document, the classes that use internally the above mentioned class template are Dispatcher, Emitter and Registry. Therefore and as an example, if you use the Registry class template in your shared library and want to set symbols visibility to hidden by default, the following lines are required to allow it to function properly with a client that also uses the Registry somehow:
Otherwise, the risk is that type identifiers are different between the shared library and the application and this will prevent the whole thing from functioning correctly for obvious reasons.
+The documentation is based on doxygen. To build it:
$ cd build $ cmake .. -DBUILD_DOCS=ON $ make
The API reference will be created in HTML format within the directory build/docs/html. To navigate it with your favorite browser:
$ cd build $ your_favorite_browser docs/html/index.html -
The API reference is also available online for the latest version.
-To compile and run the tests, EnTT requires googletest.
cmake will download and compile the library before compiling anything else. In order to build without tests set CMake option BUILD_TESTING=OFF.
$ make testNote that benchmarks are not part of this set.
-EnTT is a bitset-free entity-component system that doesn't require users to specify the component set at compile-time.
This is why users can instantiate the core class simply like:
In place of its more annoying and error-prone counterpart:
-EnTT is entirely designed around the principle that users have to pay only for what they want.
When it comes to using an entity-component system, the tradeoff is usually between performance and memory usage. The faster it is, the more memory it uses. However, slightly worse performance along non-critical paths are the right price to pay to reduce memory usage and I've always wondered why this kind of tools do not leave me the choice.
EnTT follows a completely different approach. It squeezes the best from the basic data structures and gives users the possibility to pay more for higher performance where needed.
The disadvantage of this approach is that users need to know the systems they are working on and the tools they are using. Otherwise, the risk to ruin the performance along critical paths is high.
So far, this choice has proven to be a good one and I really hope it can be for many others besides me.
-The Registry to store, the views to iterate. That's all.
An entity (the E of an ECS) is an opaque identifier that users should just use as-is and store around if needed. Do not try to inspect an entity identifier, its format can change in future and a registry offers all the functionalities to query them out-of-the-box. The underlying type of an entity (either std::uint16_t, std::uint32_t or std::uint64_t) can be specified when defining a registry (actually the DefaultRegistry is nothing more than a Registry where the type of the entities is std::uint32_t).
Components (the C of an ECS) should be plain old data structures or more complex and movable data structures with a proper constructor. Actually, the sole requirement of a component type is that it must be both move constructible and move assignable. They are list initialized by using the parameters provided to construct the component itself. No need to register components or their types neither with the registry nor with the entity-component system at all.
Systems (the S of an ECS) are just plain functions, functors, lambdas or whatever users want. They can accept a Registry or a view of any type and use them the way they prefer. No need to register systems or their types neither with the registry nor with the entity-component system at all.
The following sections will explain in short how to use the entity-component system, the core part of the whole framework.
- In fact, the framework is composed of many other classes in addition to those describe below. For more details, please refer to the inline documentation.
The following sections will explain in short how to use the entity-component system, the core part of the whole library.
+ In fact, the project is composed of many other classes in addition to those describe below. For more details, please refer to the inline documentation.
A registry can store and manage entities, as well as create views to iterate the underlying data structures.
Registry is a class template that lets users decide what's the preferred type to represent an entity. Because std::uint32_t is large enough for almost all the cases, there exists also an alias named DefaultRegistry for Registry<std::uint32_t>.
Finally, references to components can be retrieved simply by doing this:
The get member function template gives direct access to the component of an entity stored in the underlying data structures of the registry.
In those cases where all what is needed is a single instance component, tags are the right tool to achieve the purpose.
Tags undergo the same requirements of components. They can be either plain old data structures or more complex and movable data structures with a proper constructor.
@@ -346,7 +263,7 @@ Single instance components
As shown above, in almost all the cases the entity identifier isn't required. Since a single instance component can have only one associated entity, it doesn't make much sense to mention it explicitly.
To find out who the owner is, just do the following:
Note that iterating tags isn't possible for obvious reasons. Tags give direct access to single entities and nothing more.
-Because of how the registry works internally, it stores a couple of signal handlers for each pool in order to notify some of its data structures on the construction and destruction of components.
These signal handlers are also exposed and made available to users. This is the basic brick to build fancy things like dependencies and reactive systems.
To a certain extent, these limitations do not apply. However, it is risky to try to force them and users should respect the limitations unless they know exactly what they are doing. Subtle bugs are the price to pay in case of errors otherwise.
In general, events and therefore listeners must not be used as replacements for systems. They should not contain much logic and interactions with a registry should be kept to a minimum, if possible. Note also that the greater the number of listeners, the greater the performance hit when components are created or destroyed.
-As an extension, signals are also provided with tags. Although they are not strictly required internally, it makes sense that a user expects signal support even when it comes to tags actually.
Signals for tags undergo exactly the same requirements of those introduced for components. Also the function type for a listener is the same and it's invoked with the same guarantees discussed above.
To get the sinks for a tag just use tag tag_t to disambiguate overloads of member functions as in the following example:
Listeners for tags and components are managed separately and do not influence each other in any case. Therefore, note that the greater the number of listeners for a type, the greater the performance hit when a tag of the given type is created or destroyed.
-Defining components at runtime is useful to support plugin systems and mods in general. However, it seems impossible with a tool designed around a bunch of templates. Indeed it's not that difficult.
Of course, some features cannot be easily exported into a runtime environment. As an example, sorting a group of components defined at runtime isn't for free if compared to most of the other operations. However, the basic functionalities of an entity-component system such as EnTT fit the problem perfectly and can also be used to manage runtime components if required.
All that is necessary to do it is to know the identifiers of the components. An identifier is nothing more than a number or similar that can be used at runtime to work with the type system.
In EnTT, identifiers are easily accessible:
Once the identifiers are made available, almost everything becomes pretty simple.
-Once the identifiers are made available, almost everything becomes pretty simple.
+EnTT comes with an example (actually a test) that shows how to integrate compile-time and runtime components in a stack based JavaScript environment. It uses Duktape under the hood, mainly because I wanted to learn how it works at the time I was writing the code.
The code is not production-ready and overall performance can be highly improved. However, I sacrificed optimizations in favor of a more readable piece of code. I hope I succeeded.
@@ -388,7 +305,7 @@ A journey through a plugin
The basic idea is that of creating a compile-time component aimed to map all the runtime components assigned to an entity.
Identifiers come in use to address the right function from a map when invoked from the runtime environment and to filter entities when iterating.
With a bit of gymnastic, one can narrow views and improve the performance to some extent but it was not the goal of the example.
It goes without saying that sorting entities and components is possible with EnTT.
In fact, there are two functions that respond to slightly different needs:
In this case, instances of Movement are arranged in memory so that cache misses are minimized when the two components are iterated together.
The Registry class offers basic support to serialization.
It doesn't convert components and tags to bytes directly, there wasn't the need of another tool for serialization out there. Instead, it accepts an opaque object with a suitable interface (namely an archive) to serialize its internal data structures and restore them later. The way types and instances are converted to a bunch of bytes is completely in charge to the archive and thus to final users.
component and tag store items along with entities. It means that they work properly without a call to the entities member function.
Once a snapshot is created, there exist mainly two ways to load it: as a whole and in a kind of continuous mode.
The following sections describe both loaders and archives in details.
A snapshot loader requires that the destination registry be empty and loads all the data at once while keeping intact the identifiers that the entities originally had.
To do that, the registry offers a member function named restore that returns a temporary object properly initialized to restore a snapshot.
The entities and destroyed member functions restore the sets of entities and the versions that the entities originally had at the source.
The component member function restores all and only the components specified and assigns them to the right entities. Note that the template parameter list must be exactly the same used during the serialization. The same applies to the tag member function.
The orphans member function literally destroys those entities that have neither components nor tags. It's usually useless if the snapshot is a full dump of the source. However, in case all the entities are serialized but only few components and tags are saved, it could happen that some of the entities have neither components nor tags once restored. The best users can do to deal with them is to destroy those entities and thus update their versions.
A continuous loader is designed to load data from a source registry to a (possibly) non-empty destination. The loader can accommodate in a registry more than one snapshot in a sort of continuous loading that updates the destination one step at a time.
Identifiers that entities originally had are not transferred to the target. Instead, the loader maps remote identifiers to local ones while restoring a snapshot. Because of that, this kind of loader offers a way to update automatically identifiers that are part of components or tags (as an example, as data members or gathered in a container).
@@ -444,7 +361,7 @@ Continuous loader
In case the component or the tag contains entities itself (either as data members of type entity_type or as containers of entities), the loader can update them automatically. To do that, it's enough to specify the data members to update as shown in the example.
The orphans member function literally destroys those entities that have neither components nor tags after a restore. It has exactly the same purpose described in the previous section and works the same way.
Finally, shrink helps to purge local entities that no longer have a remote conterpart. Users should invoke this member function after restoring each snapshot, unless they know exactly what they are doing.
Archives must publicly expose a predefined set of member functions. The API is straightforward and consists only of a group of function call operators that are invoked by the snapshot class and the loaders.
In particular:
@@ -460,12 +377,12 @@ ArchivesWhere Entity is the type of the entities used by the registry. Each time the function is invoked, the archive must read the next element from the underlying storage and copy it in the given variable. Note that all the member functions of a loader class make also an initial call to this endpoint to read the size of the set they are going to load.
In addition, the archive must accept a pair of entity and either component or tag for each type to be restored. Therefore, given a type T, the archive must contain a function call operator with the following signature:
Every time such an operator is invoked, the archive must read the next elements from the underlying storage and copy them in the given variables.
-EnTT comes with some examples (actually some tests) that show how to integrate a well known library for serialization as an archive. It uses Cereal C++ under the hood, mainly because I wanted to learn how it works at the time I was writing the code.
The code is not production-ready and it isn't neither the only nor (probably) the best way to do it. However, feel free to use it at your own risk.
The basic idea is to store everything in a group of queues in memory, then bring everything back to the registry with different loaders.
-A prototype defines a type of an application in terms of its parts. They can be used to assign components to entities of a registry at once.
Roughly speaking, in most cases prototypes can be considered just as templates to use to initialize entities according to concepts. In fact, users can create how many prototypes they want, each one initialized differently from the others.
In the examples above, the prototype uses its underlying registry to create entities and components both for its purposes and when it's cloned. To use a different repository to clone a prototype, all the member functions accept also a reference to a valid registry as a first argument.
Prototypes are a very useful tool that can save a lot of typing sometimes. Furthermore, the codebase may be easier to maintain, since updating a prototype is much less error prone than jumping around in the codebase to update all the snippets copied and pasted around to initialize entities and components.
-The so called helpers are small classes and functions mainly designed to offer built-in support for the most basic functionalities.
The list of helpers will grow longer as time passes and new ideas come out.
A dependency function is a predefined listener, actually a function template to use to automatically assign components to an entity when a type has a dependency on some other types.
The following adds components AType and AnotherType whenever MyType is assigned to an entity:
A component is assigned to an entity and thus default initialized only in case the entity itself hasn't it yet. It means that already existent components won't be overriden.
A dependency can easily be broken by means of the same function template:
There's nothing magical about the way labels can be assigned to entities while avoiding a performance hit at runtime. Nonetheless, the syntax can be annoying and that's why a more user-friendly shortcut is provided to do it.
+ This shortcut is the alias template entt::label.
If used in combination with hashed strings, it helps to use labels where types would be required otherwise. As an example:
+In EnTT, there exists a sort of null entity made available to users that is accessible via the entt::null variable.
- The framework guarantees that the following expression always returns false:
In other terms, a registry will reject the null entity in all cases because it isn't considered valid. It means that the null entity cannot own components or tags for obvious reasons.
The type of the null entity is internal and should not be used for any purpose other than defining the null entity itself. However, there exist implicit conversions from the null entity to identifiers of any allowed type:
Similarly, the null entity can be compared to any other identifier:
-First of all, it is worth answering an obvious question: why views?
Roughly speaking, they are a good tool to enforce single responsibility. A system that has access to a registry can create and destroy entities, as well as assign and remove components. On the other side, a system that has access to a view can only iterate entities and their components, then read or update the data members of the latter.
@@ -565,13 +487,13 @@ View: to persist or not to persist?
To easily iterate entities and components, all the views offer the common begin and end member functions that allow users to use a view in a typical range-for loop. Almost all the views offer also a more functional each member function that accepts a callback for convenience.
Continue reading for more details or refer to the inline documentation.
A standard view behaves differently if it's constructed for a single component or if it has been requested to iterate multiple components. Even the API is different in the two cases.
All that they share is the way they are created by means of a registry:
For all that remains, it's worth discussing them separately.
Single component standard views are specialized in order to give a boost in terms of performance in all the situation. This kind of views can access the underlying data structures directly and avoid superfluous checks.
They offer a bunch of functionalities to get the number of entities they are going to return and a raw access to the entity list as well as to the component list. It's also possible to ask a view if it contains a given entity.
@@ -581,7 +503,7 @@ Single component standard view
Or rely on the each member function to iterate entities and get all their components at once:
The each member function is highly optimized. Unless users want to iterate only entities, using each should be the preferred approach.
Note: prefer the get member function of a view instead of the get member function template of a registry during iterations, if possible. However, keep in mind that it works only with the components of the view itself.
Multi component standard views iterate entities that have at least all the given components in their bags. During construction, these views look at the number of entities available for each component and pick up a reference to the smallest set of candidates in order to speed up iterations.
They offer fewer functionalities than their companion views for single component. In particular, a multi component standard view exposes utility functions to get the estimated number of entities it is going to return and to know whether it's empty or not. It's also possible to ask a view if it contains a given entity.
@@ -591,7 +513,7 @@ Multi component standard view
Or rely on the each member function to iterate entities and get all their components at once:
The each member function is highly optimized. Unless users want to iterate only entities or get only some of the components, using each should be the preferred approach.
Note: prefer the get member function of a view instead of the get member function template of a registry during iterations, if possible. However, keep in mind that it works only with the components of the view itself.
A persistent view returns all the entities and only the entities that have at least the given components. Moreover, it's guaranteed that the entity list is tightly packed in memory for fast iterations.
In general, persistent views don't stay true to the order of any set of components unless users explicitly sort them.
Or rely on the each member function to iterate entities and get all their components at once:
Performance are more or less the same. The best approach depends mainly on whether all the components have to be accessed or not.
Note: prefer the get member function of a view instead of the get member function template of a registry during iterations, if possible. However, keep in mind that it works only with the components of the view itself.
Raw views return all the components of a given type. This kind of views can access components directly and avoid extra indirections like when components are accessed via an entity identifier.
They offer a bunch of functionalities to get the number of instances they are going to return and a raw access to the entity list as well as to the component list.
@@ -616,7 +538,7 @@ Raw View
Or rely on the each member function:
Performance are exactly the same in both cases.
Note: raw views don't have a get member function for obvious reasons.
Runtime views iterate entities that have at least all the given components in their bags. During construction, these views look at the number of entities available for each component and pick up a reference to the smallest set of candidates in order to speed up iterations.
They offer more or less the same functionalities of a multi component standard view. However, they don't expose a get member function and users should refer to the registry that generated the view to access components. In particular, a runtime view exposes utility functions to get the estimated number of entities it is going to return and to know whether it's empty or not. It's also possible to ask a view if it contains a given entity.
@@ -626,7 +548,7 @@ Runtime View
Or rely on the each member function to iterate entities:
Performance are exactly the same in both cases.
Note: runtime views are meant for all those cases where users don't know at compile-time what components to use to iterate entities. This is particularly well suited to plugin systems and mods in general. Where possible, don't use runtime views, as their performance are slightly inferior to those of the other views.
-Views are narrow windows on the entire list of entities. They work by filtering entities according to their components.
In some cases there may be the need to iterate all the entities still in use regardless of their components. The registry offers a specific member function to do that:
To test the orphanity of a single entity, use the member function orphan instead. It accepts a valid entity identifer as an argument and returns true in case the entity is an orphan, false otherwise.
In general, all these functions can result in poor performance.
each is fairly slow because of some checks it performs on each and every entity. For similar reasons, orphans can be even slower. Both functions should not be used frequently to avoid the risk of a performance hit.
Most of the ECS available out there have some annoying limitations (at least from my point of view): entities and components cannot be created nor destroyed during iterations.
EnTT partially solves the problem with a few limitations:
A notable side effect of this feature is that the number of required allocations is further reduced in most of the cases.
-In general, the entire registry isn't thread safe as it is. Thread safety isn't something that users should want out of the box for several reasons. Just to mention one of them: performance.
Views and consequently the approach adopted by EnTT are the great exception to the rule. It's true that views and thus their iterators aren't thread safe by themselves. Because of this users shouldn't try to iterate a set of components and modify the same set concurrently. However:
This kind of entity-component systems can be used in single threaded applications as well as along with async stuff or multiple threads. Moreover, typical thread based models for ECS don't require a fully thread safe registry to work. Actually, users can reach the goal with the registry as it is while working with most of the common models.
Because of the few reasons mentioned above and many others not mentioned, users are completely responsible for synchronization whether required. On the other hand, they could get away with it without having to resort to particular expedients.
-The EnTT framework comes with a bunch of core functionalities mostly used by the other parts of the library itself.
- Hardly users of the framework will include these features in their code, but it's worth describing what EnTT offers so as not to reinvent the wheel in case of need.
EnTT comes with a bunch of core functionalities mostly used by the other parts of the library itself.
+ Hardly users will include these features in their code, but it's worth describing what EnTT offers so as not to reinvent the wheel in case of need.
Sometimes it's useful to be able to give unique identifiers to types at compile-time.
There are plenty of different solutions out there and I could have used one of them. However, I decided to spend my time to define a compact and versatile tool that fully embraces what the modern C++ has to offer.
This is all what the class template has to offer: a static get member function that returns a numerical identifier for the given type. It can be used in any context where constant expressions are required.
As long as the list remains unchanged, identifiers are also guaranteed to be the same for every run. In case they have been used in a production environment and a type has to be removed, one can just use a placeholder to left the other identifiers unchanged:
A bit ugly to see, but it works at least.
-Sometimes it's useful to be able to give unique identifiers to types at runtime.
- There are plenty of different solutions out there and I could have used one of them. In fact, I adapted the most common one to my requirements and used it extensively within the entire framework.
It's the Family class. Here is an example of use directly from the entity-component system:
This is all what a family has to offer: a type member function that returns a numerical identifier for the given type.
Please, note that identifiers aren't guaranteed to be the same for every run. Indeed it mostly depends on the flow of execution.
-A hashed string is a zero overhead resource identifier. Users can use human-readable identifiers in the codebase while using their numeric counterparts at runtime, thus without affecting performance.
The class has an implicit constexpr constructor that chews a bunch of characters. Once created, all what one can do with it is getting back the original string or converting it into a number.
The good part is that a hashed string can be used wherever a constant expression is required and no string-to-number conversion will take place at runtime if used carefully.
Example of use:
-There is also a user defined literal dedicated to hashed strings to make them more user-friendly:
+The hashed string class uses internally FNV-1a to compute the numeric counterpart of a string. Because of the pigeonhole principle, conflicts are possible. This is a fact.
There is no silver bullet to solve the problem of conflicts when dealing with hashing functions. In this case, the best solution seemed to be to give up. That's all.
After all, human-readable resource identifiers aren't something strictly defined and over which users have not the control. Choosing a slightly different identifier is probably the best solution to make the conflict disappear in this case.
The monostate pattern is often presented as an alternative to a singleton based configuration system. This is exactly its purpose in EnTT. Moreover, this implementation is thread safe by design (hopefully).
Keys are represented by hashed strings, values are basic types like ints or bools. Values of different types can be associated to each key, even more than one at a time. Because of this, users must pay attention to use the same type both during an assignment and when they try to read back their data. Otherwise, they will probably incur in unexpected results.
Example of use:
-Usually service locators are tightly bound to the services they expose and it's hard to define a general purpose solution. This template based implementation tries to fill the gap and to get rid of the burden of defining a different specific locator for each application.
This class is tiny, partially unsafe and thus risky to use. Moreover it doesn't fit probably most of the scenarios in which a service locator is required. Look at it as a small tool that can sometimes be useful if the user knows how to handle it.
The locator can also be queried to know if an active service is currently set and to retrieve it if necessary (either as a pointer or as a reference):
A common use is to wrap the different locators in a container class, creating aliases for the various services:
-Sometimes processes are a useful tool to work around the strict definition of a system and introduce logic in a different way, usually without resorting to the introduction of other components.
-The EnTT framework offers a minimal support to this paradigm by introducing a few classes that users can use to define and execute cooperative processes.
EnTT offers a minimal support to this paradigm by introducing a few classes that users can use to define and execute cooperative processes.
A typical process must inherit from the Process class template that stays true to the CRTP idiom. Moreover, derived classes must specify what's the intended type for elapsed times.
A process should expose publicly the following member functions whether required (note that it isn't required to define a function unless the derived class wants to override the default behavior):
@@ -733,7 +656,7 @@ The processDerived classes can also change the internal state of a process by invoking succeed and fail, as well as pause and unpause the process itself. All these are protected member functions made available to be able to manage the life cycle of a process from a derived class.
Here is a minimal example for the sake of curiosity:
-Lambdas and functors can't be used directly with a scheduler for they are not properly defined processes with managed life cycles.
This class helps in filling the gap and turning lambdas and functors into full featured processes usable by a scheduler.
Both succeed and fail accept no parameters at all.
Note that usually users shouldn't worry about creating adaptors at all. A scheduler creates them internally each and every time a lambda or a functor is used as a process.
-A cooperative scheduler runs different processes and helps managing their life cycles.
Each process is invoked once per tick. If it terminates, it's removed automatically from the scheduler and it's never invoked again. Otherwise it's a good candidate to run once more the next tick.
@@ -765,13 +688,13 @@ The scheduler
As a minimal example of use:
To update a scheduler and thus all its processes, the update member function is the way to go:
In addition to these functions, the scheduler offers an abort member function that can be used to discard all the running processes at once:
Resource management is usually one of the most critical part of a software like a game. Solutions are often tuned to the particular application. There exist several approaches and all of them are perfectly fine as long as they fit the requirements of the piece of software in which they are used.
Examples are loading everything on start, loading on request, predictive loading, and so on.
The EnTT framework doesn't pretend to offer a one-fits-all solution for the different cases. Instead, it offers a minimal and perhaps trivial cache that can be useful most of the time during prototyping and sometimes even in a production environment.
+
EnTT doesn't pretend to offer a one-fits-all solution for the different cases. Instead, it offers a minimal and perhaps trivial cache that can be useful most of the time during prototyping and sometimes even in a production environment.
For those interested in the subject, the plan is to improve it considerably over time in terms of performance, memory usage and functionalities. Hoping to make it, of course, one step at a time.
There are three main actors in the model: the resource, the loader and the cache.
The resource is whatever the user wants it to be. An image, a video, an audio, whatever. There are no limits.
@@ -815,14 +738,14 @@ The resource, the loader and the cache
Finally, in case there is the need to load a resource and thus to get a handle without storing the resource itself in the cache, users can rely on the temp member function template.
The declaration is similar to the one of load but for the fact that it doesn't return a boolean value. Instead, it returns a (possibly invalid) handle for the resource:
Do not forget to test the handle for validity. Otherwise, getting the reference to the resource it points may result in undefined behavior.
-Signals are usually a core part of games and software architectures in general.
Roughly speaking, they help to decouple the various parts of a system while allowing them to communicate with each other somehow.
The so called _modern C++_ comes with a tool that can be useful in these terms, the std::function. As an example, it can be used to create delegates.
However, there is no guarantee that an std::function does not perform allocations under the hood and this could be problematic sometimes. Furthermore, it solves a problem but may not adapt well to other requirements that may arise from time to time.
In case that the flexibility and potential of an std::function are not required or where you are looking for something different, the EnTT framework offers a full set of classes to solve completely different problems.
In case that the flexibility and potential of an std::function are not required or where you are looking for something different, EnTT offers a full set of classes to solve completely different problems.
Signal handlers work with naked pointers, function pointers and pointers to member functions. Listeners can be any kind of objects and the user is in charge of connecting and disconnecting them from a signal to avoid crashes due to different lifetimes. On the other side, performance shouldn't be affected that much by the presence of such a signal handler.
A signal handler can be used as a private data member without exposing any publish functionality to the clients of a class. The basic idea is to impose a clear separation between the signal itself and its sink class, that is a tool to be used to connect and disconnect listeners on the fly.
Once listeners are attached (or even if there are no listeners at all), events and data in general can be published through a signal by means of the publish member function:
To collect data, the collect member function should be used instead. Below is a minimal example to show how to use it:
As shown above, a collector must expose a function operator that accepts as an argument a type to which the return type of the listeners can be converted. Moreover, it has to return a boolean value that is false to stop collecting data, true otherwise. This way one can avoid calling all the listeners in case it isn't necessary.
-A delegate can be used as general purpose invoker with no memory overhead for free functions and member functions provided along with an instance on which to invoke them.
It does not claim to be a drop-in replacement for an std::function, so do not expect to use it whenever an std::function fits well. However, it can be used to send opaque delegates around to be used to invoke functions as needed.
It hasn't a disconnect counterpart. Instead, there exists a reset member function to clear it.
The empty member function can be used to know if a delegate is empty:
Finally, to invoke a delegate, the function call operator is the way to go as usual:
-Probably too much small and pretty poor of functionalities, but the delegate class can help in a lot of cases and it has shown that it is worth keeping it within the framework.
-Probably too much small and pretty poor of functionalities, but the delegate class can help in a lot of cases and it has shown that it is worth keeping it within the library.
+The event dispatcher class is designed so as to be used in a loop. It allows users both to trigger immediate events or to queue events to be published all together once per tick.
This class shares part of its API with the one of the signal handler, but it doesn't require that all the types of events are specified when declared:
On the other hand, the enqueue member function queues messages together and allows to maintain control over the moment they are sent to listeners. The signature of this method is more or less the same of trigger:
Events are stored aside until the update member function is invoked, then all the messages that are still pending are sent to the listeners at once:
This way users can embed the dispatcher in a loop and literally dispatch events once per tick to their systems.
-A general purpose event emitter thought mainly for those cases where it comes to working with asynchronous stuff.
Originally designed to fit the requirements of uvw (a wrapper for libuv written in modern C++), it was adapted later to be included in this library.
To send an event to all the listeners that are interested in it, the publish member function offers a convenient approach that relieves the user from having to create the event:
Finally, the empty member function tests if there exists at least either a listener registered with the event emitter or to a given type of event:
In general, the event emitter is a handy tool when the derived classes wrap asynchronous operations, because it introduces a nice-to-have model based on events and listeners that kindly hides the complexity behind the scenes. However it is not limited to such uses.
-EnTT is available for some of the most known packaging tools. In particular:
Consider this list a work in progress and help me to make it longer.
-EnTT is widely used in private and commercial applications. I cannot even mention most of them because of some signatures I put on some documents time ago.
Fortunately, there are also people who took the time to implement open source projects based on EnTT and did not hold back when it came to documenting them.
Below an incomplete list of projects and articles:
EnTT framework.EnTT.UE4.UE4 and EnTT.If you know of other resources out there that are about EnTT, feel free to open an issue or a PR and I'll be glad to add them to the list.
If you want to participate, please see the guidelines for contributing before to create issues or pull requests.
- Take also a look at the contributors list to know who has participated so far.
Code and documentation Copyright (c) 2018 Michele Caini.
- Code released under the MIT license. Docs released under Creative Commons.
Developing and maintaining EnTT takes some time and lots of coffee. I'd like to add more and more functionalities in future and turn it in a full-featured framework.
- If you want to support this project, you can offer me an espresso. I'm from Italy, we're used to turning the best coffee ever in code. If you find that it's not enough, feel free to support me the way you prefer.
- Take a look at the donation button at the top of the page for more details or just click here.
If you start using EnTT and need help, if you want a new feature and want me to give it the highest priority, if you have any other reason to contact me: do not hesitate. I'm available for hiring.
- Feel free to take a look at my profile and contact me by mail.
Code and documentation Copyright (c) 2017-2018 Michele Caini.
+ Logo Copyright (c) 2018 Richard Caseres.
Code released under the MIT license. Documentation released under CC BY 4.0.
+ Logo released under CC BY-SA 4.0.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/loader_8hpp_source.html b/loader_8hpp_source.html
index 58f27ec6a..840907e84 100644
--- a/loader_8hpp_source.html
+++ b/loader_8hpp_source.html
@@ -5,7 +5,7 @@
-The default registry is the best choice for almost all the applications.
Users should have a really good reason to choose something different.
Definition at line 1598 of file registry.hpp.
+Definition at line 1623 of file registry.hpp.
+ + + + +| using entt::label = typedef std::integral_constant<typename HashedString::hash_type, Value> | +
Alias template to ease the assignment of labels to entities.
+If used in combination with hashed strings, it simplifies the assignment of labels to entities and the use of labels in general where a type would be required otherwise.
+ As an example and where the user defined literal for hashed strings hasn't been changed:
| Value | The numeric representation of an instance of hashed string. |
Definition at line 99 of file helper.hpp.
Definition at line 28 of file helper.hpp.
+Definition at line 30 of file helper.hpp.
@@ -397,7 +431,7 @@ template<typename... Dependency, typename Entity > -Definition at line 53 of file helper.hpp.
+Definition at line 55 of file helper.hpp.
@@ -445,7 +479,7 @@ template<typename... Dependency, typename Entity > -Definition at line 76 of file helper.hpp.
+Definition at line 78 of file helper.hpp.
diff --git a/namespacemembers.html b/namespacemembers.html index a60fd2667..daf84fec4 100644 --- a/namespacemembers.html +++ b/namespacemembers.html @@ -5,7 +5,7 @@ -|
+ EnTT
+ 2.7.2
+
+ |
+
| Contributing |
+ 1.8.13
+
+
+
diff --git a/process_8hpp_source.html b/process_8hpp_source.html
index cf6e634ce..1df9bc497 100644
--- a/process_8hpp_source.html
+++ b/process_8hpp_source.html
@@ -5,7 +5,7 @@
-

diff --git a/structentt_1_1InsertionSort-members.html b/structentt_1_1InsertionSort-members.html
index d52258dc7..16f834ae9 100644
--- a/structentt_1_1InsertionSort-members.html
+++ b/structentt_1_1InsertionSort-members.html
@@ -5,7 +5,7 @@
-
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
- |
entt
- 2.7.1
+ EnTT
+ 2.7.2
entt::InsertionSort Struct Reference template<typename It , typename Compare = std::less<>> | void | operator() (It first, It last, Compare compare=Compare{}) const | | Sorts the element in a range. More... | | Sorts the elements in a range. More... | | | |||
Sorts the element in a range.
-Sorts the element in a range using the given binary comparison function.
+Sorts the elements in a range.
+Sorts the elements in a range using the given binary comparison function.
| It | Type of random access iterator. | ||||||||||||||||
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|||||||||||||||||
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|||||||||||||||||
|
+ EnTT
+ 2.7.2
+
+ |
+
This is the complete list of members for entt::OneShotBubbleSort, including all inherited members.
+| operator()(It first, It last, Compare compare=Compare{}) const | entt::OneShotBubbleSort | inline |
+ 1.8.13
+
+
+
diff --git a/structentt_1_1OneShotBubbleSort.html b/structentt_1_1OneShotBubbleSort.html
new file mode 100644
index 000000000..d0f4fdd77
--- /dev/null
+++ b/structentt_1_1OneShotBubbleSort.html
@@ -0,0 +1,166 @@
+
+
+
+
+
+
+
+|
+ EnTT
+ 2.7.2
+
+ |
+
Function object for performing bubble sort (single iteration). + More...
+ +#include <algorithm.hpp>
+Public Member Functions | |
| template<typename It , typename Compare = std::less<>> | |
| void | operator() (It first, It last, Compare compare=Compare{}) const |
| Tries to sort the elements in a range. More... | |
Function object for performing bubble sort (single iteration).
+ +Definition at line 76 of file algorithm.hpp.
+
+
|
+ +inline | +
Tries to sort the elements in a range.
+Performs a single iteration to sort the elements in a range using the given binary comparison function. The range may not be completely sorted after running this function.
+| It | Type of random access iterator. |
| Compare | Type of comparison function object. |
| first | An iterator to the first element of the range to sort. |
| last | An iterator past the last element of the range to sort. |
| compare | A valid comparison function object. |
Definition at line 91 of file algorithm.hpp.
+ +
+ 1.8.13
+
+
+
diff --git a/structentt_1_1ProcessAdaptor-members.html b/structentt_1_1ProcessAdaptor-members.html
index 128a353c0..9890a3424 100644
--- a/structentt_1_1ProcessAdaptor-members.html
+++ b/structentt_1_1ProcessAdaptor-members.html
@@ -5,7 +5,7 @@
-Sorts the element in a range.
-Sorts the element in a range using the given binary comparison function.
+Sorts the elements in a range.
+Sorts the elements in a range using the given binary comparison function.
| It | Type of random access iterator. |
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|
|
|
- entt
- 2.7.1
+ EnTT
+ 2.7.2
|