to cover the identified use-cases a wide variety of functors must be accepted and adapted appropriately. A special twist arises from the fact that the complete thread-wrapper component stack works without RTTI; a derived class can not access the thread-wrapper internals while the policy component to handle those hooks can not directly downcast to some derived user provided class. But obviously at usage site it can be expected to access both realms from such a callback. The solution is to detect the argument type of the given functor and to build a two step path for a safe static cast. |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||