ENIGMA Development Environment

I can see why he would choose C over C++. One is that C++ has no standard ABI. Thanks to Rusky and DaSpirit I am starting to like Rust. I also hate every Windows port of GCC. Rust has reached stable 1.0 now so it is something to consider. It's nice to be able to return multiple values and be more expressive than C++.

Alright that sounds good. You may want to read my reply in the other post though. I did find an existing issue that I think may be causing your problems. More debugging is needed but I don't have time right now.

http://enigma-dev.org/forums/index.php?topic=2678.0

I should mention the current task I am working on with ENIGMA is cleaning up the joystick and windows executable code. I've improved compatibility with the XInput gamepad functions. So maybe I'll try to bundle fixes for the Linux joysticks as well after testing.

https://github.com/enigma-dev/enigma-dev/pull/966

If anything else comes up just let us know.

Read the following tutorial that explains how to debug the game with GDB and show us a stack trace:

http://enigma-dev.org/forums/index.php?topic=1815

I see and I also realize that is undesirable. This would take quite a bit of debugging to solve, and I am not even sure where to look to find this bug. It could also be related to the following GitHub issue which we are keeping open due to known issues with the order of collision events and inheritance.

https://github.com/enigma-dev/enigma-dev/issues/870

Awesome! Yeah it's an old GameMaker thing. It probably would have been better in retrospect if image_speed was the fps of the animation, it would be less confusing I think. But for compatibility reasons it's better if we just let well enough alone.

Generally image_speed = room_speed / sprite_get_number(sprite_index); will make the sprite frame always the same as it plays back in the game.

I'll take another look here after bit when I get back home. We have some known issues with those functions.

It looks like a lot of those issues stem from the fact that ENIGMA uses C++. For example, the first issue is you have some variable named delete which is an operator and therefore a reserved keyword in C++.

I think it's great to have multiple IDE's and competition which is better for users. People just have different styles and at the same time the same person can have different uses for a tool. For example, even someone who prefers an alternative IDE likes to have something to fall back on. Even myself included if I was developing a second IDE, it would be helpful to have a reliable tool to check things out with. LateralGM fills that role, the whole point of it is to be exactly like GameMaker. If I was still working on a second IDE I would probably end up using LateralGM a couple times to convert a file or do some operation not yet supported by my new IDE, etc. It is similar to how OpenJDK is a "reference" implementation for the Java Standard Edition.

But yeah, not going to deny that LateralGM is boring and while it has made some progress towards stability, it has a ways to go yet. Feel free to post as often as you like, you know we welcome third party tools here.