#ifdef __orxWINDOWS__ #include "windows.h" extern "C" { _declspec(dllexport) DWORD NvOptimusEnablement = 1; _declspec(dllexport) int AmdPowerXpr

#ifndef __orxPLUGIN__

#ifdef __orxWINDOWS__

<pre><code>#ifndef PINBALLBASE_H

<br />And that works fine.<br />Say for instance you try to move the code into a header and class files so that everything is declared and initialised separately:<br />mystuff.h<b

story short, it use some conditional compilation #if/#endif to mix editor/runtime stuff which couldn't be so easily separated and then there is the problem of the building the player when you mix edi

#ifdef __TOUCH__

This version should also work, without making assumption based on enabled debug levels:<br /><pre><code>#ifndef __orxDEBUG__

<div class="QuoteText">One more thing, we could add tool specific stuffs using conditional compilation, so things specific to Box2D could be added under <a rel="nofollow"

PHYSICS_BOX2D &lt;a href="https://forum.orx-project.org/index.php?p=/search&amp;Search=#endif&amp;Mode=like&quot;&gt;#endif&lt;/a&gt;, some engines for example cocos2

#ifndef HASMASS_H_

#ifdef __orxMSVC__

#ifndef COMMON_H_

#ifndef Paradigm

<br />I prepared a proof of concept implementation. You can find a patch in the attachment. For now I've enclosed the implementation inside #ifdef's as I'm not sure if an additional char pointer

<pre><code>#ifndef INPUTCONTROLLER_H

<pre><code>#ifndef INPUTCONTROLLER_H

<div class="QuoteText">I'm afraid you'll have to suffer through <a rel="nofollow" href="https://forum.orx-project.org/index.php?p=/search&amp;Search=#ifdefs&a

for now. &lt;img class=" title=":/"><br />But depending on your needs, if you simply want to generically push vertices+attributes for an object I can probably wrap this on

platform independent, or should I suffer the #ifdef's if I want that much freedom? If the answer's going to be much longer than yes/no, please tell me, so I can do this properly in a dedicated thread