ENIGMA Development Environment

Ok........ so maybe I came off a bit brazen and critical in my comments about 'bad coding' and some other things i've written. My intention was not to be that way. I apologize.

My intent was to show a more efficient way to solve the problem but somewhere I got carried away. Again I apologize.

I too prefer to use GML/EDL over DRAG N DROP, although at times it becomes necessary to use it. i also Believe I may have misread some of your comments.

Lastly i want to clear up what you may be perceiving as a misunderstanding on your part. I do not consider you in the same class of people whom "I believe it is a tad too much for one to expect GM files to be that compliant with ENIGMA without some type of error at some time". i was generalizing since based on people's past comments on this forum, Game Maker's forum and other places I had researched, that was commonality among them.

i have the deepest praise for ENIGMA and its creators. I think its a brilliant, wonderful and fantastic piece of software. The fact that it is compliant with Game Maker which i spent the majority of my life learning, as well as being able to run on LINUX, is an added bonus.

with all due respect, I don't agree such qualify as a basis for finding a bug.

First let me say that I believe it is a tad too much for one to expect GM files to be that compliant with ENIGMA without some type of error at some time.

Now let's examine the files in question.

In the first one, the arrow moves towards the ball by way of the KEYBOARD event. Simple enough.

In the second one, a variable Jump is placed in the Create event of the object Ball. In the Step event in the object Arrow, it is to move towards the ball and back through change states of the variable Jump..... i.e Jump=1 and Jump=0. This action is to be done through the KEY PRESS and KEY RELEASE of the letter J in the object Ball.



Although it runs perfectly in Game Maker, we see a problem in ENIGMA in that when you press 'J' on the keyboard the ball moves and not the arrow. My concern is the placement of objects.  When I remove the arrow object, the ball is in the correct place. When placed back in, chaos returns. It seems then the arrow object or rather the code, is the problem.



https://imgur.com/9yNtyh8


I rewrote the object ball to this:

https://imgur.com/DH8naJv

and there you have it.

I believe this shows that there is no bug. I can't be sure but I believe it has to do with how ENIGMA interprets GM code as well as bad code writing. No fault on the coder. We all make mistakes and we're not perfect coders.

I've been mulling over the idea of creating a Beginners Guide to ENIGMA for quite a while now. I think one is really needed but I'm having trouble deciding how to go about it. Which is where you come in.

My ideas are as follows:

• Interactive.......where the user performs actions and  actions are performed.
• ebook form........pdf, or html with illustrations, etc
• series of videos......hosted on Youtube, Dailymotion.

I'd really like to hear you thoughts.

In the first example you could've add a KEY RELEASE J event and place a JUMP TO START action to the Arrow object to get the same result instead of using a STEP event.

what you can also do is download a screen recorder Like Snaggit, to record the strangeness you encounter, post it as well as the segment of code.

Snaggit can be downloaded from here http://download.cnet.com/Snagit/3000-2192_4-10004813.html

I also recommend you watch this video..... https://youtu.be/8kHOsRSRbaA .

Thanks

that's quite interesting to hear Goombert. I've been using ENIGMA on my LINUX machines and I've yet to encounter such a bug. Of course, I've encountered others but that's another story.

The bit of code given is excellent. However for the sake of newbies who may be reading this post, I wish to clarify a few things on two sets of code.

'draw_set_color(c_white)' used in the Draw event sets what is called the base color of the room or object referred to. The base color affects all the other elements, like fonts, text, forms primitives and 3D.
'draw_self()' used in the same Draw event is a function that forces the sprite's image, (whether you indicate one or not) to be drawn.