ENIGMA Forums
General fluff => General ENIGMA => Topic started by: polygone on August 24, 2013, 08:05:06 pm
-
There's always endless warnings that crop up when compiling. I think as developers we should have a new mandate that instead of ignoring them we should resolve them whenever we see one instead of just always ignoring them. This is the only way I think they will get weeded out of the source.
-
Speaking of something related. Does anybody know why the plugin is passing all true booleans as -1 instead of 1? It's not making any difference to the outcome but it's rather dodgy and throws warnings everywhere. It's doing it in all the game settings and room settings and such.
-
Yes we do need to do some warning cleanup you already know that slows down compiling, lots of them are probably my fault I have been ignoring quite a few. But what do you mean the plugin is passing -1's?
-
Check the output of settings or room array in preprocessor whenever ever there is a boolean variable that's set to true it's printed as -1.
-
Idk plionz, GMX stores boolean true as -1 :P
-
It's sending values of -1 with a blank game as well. -Oh because LGM sets them to -1 also in order to be compatible with GM. But LGM should set them all boolean before sending to the plugin.
-
https://github.com/enigma-dev/enigma-dev/pull/352
Merge that joystick and exe fix polygonz, enigma.exe now needs settings.ini for which the code is this...
[MAIN]
setupcompleted=1
checkforjava=0
redirectoutput=1
Delete the file called compiled, and you can set that to 1 there if you already set up ENIGMA. I've uploaded the new zip already.
-
This has nothing to do with the warnings...