All public logs
Jump to navigation
Jump to search
Combined display of all available logs of neoGFX. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).
- 15:02, 5 May 2024 Leigh talk contribs created page Naming Convention (Created page with "The neoGFX naming convention is based on the idea that to aid readability it is better to encode ''scope'' rather than ''type'' in an identifier name prefix. The idea of encoding scope in identifier names was introduced by the smartphone operating system ''Symbian OS''. The following table lists the various C++ syntactical constructs with their associated convention: {| class="wikitable" style="margin-left: 0px; margin-right: auto;" |+ neoGFX Naming Convention |- ! Co...")
- 18:37, 4 May 2024 Leigh talk contribs moved page NeoGFX Event System to Event System without leaving a redirect
- 18:33, 4 May 2024 Leigh talk contribs moved page EventSystem to NeoGFX Event System without leaving a redirect
- 18:32, 4 May 2024 Leigh talk contribs created page EventSystem (Created page with "== neoGFX Event System == The neoGFX event system is both modern and simple and is an improvement over traditional signals and slots. To create an event handler simply use a lambda expression thus: <code> button1.clicked([](){ ... code ...: }); </code> If automatic event handler de-registration (traditional role of a "slot") is wanted: <code> neoGFX::sink s; s += button1.clicked([](){ ... code ...: }); </code> When 's' is destroyed any associated event re...")