ENIGMA Development Environment

I don't understand why it freezes. I'm looking into it. It should at least report some kind of error.

I asked for the revision, not the version.
I'm unable to reproduce with the latest version available on our website, so I believe that this is a bug that we already fixed. In fact, I recall similar problems, and I remember implementing a solution, so I'd assume it's the same bug as that. Enigma just hasn't caught up with including that version yet.

Some options:
1) You can wait until the next Enigma release comes out. With a bit of luck, Joshy will have included a more recent LGM version.
2) You can try downloading LGM from the LateralGM website and replacing your outdated version with that (LGM has no issue with being renamed - but Enigma expects a certain filename, and likewise, LGM expects a certain filename for Enigma).
This may not work, due to changes in the format between beta1 and beta2.
3) You can get things from the repositories. Especially the LGM-Enigma plugin, which has 3 revisions so far, the oldest being probably the one you're using. The next revision is compatibility for LGM1.6.0b2. The latest revision is compatibility for the repository LGM.

In those religions, the afterlife was heaven, even if it was underground. The alternative was to stop existing, which was undesirable to them. They didn't have a land of torture like Christianity's Hell. People were just good because they wanted to get into their "heaven".

This sounds like a question that should be asked on the LGM forums. Of course, I'm guessing neither of you has an account there, and just yesterday I disabled registration for a little while so we can get some new forum mechanisms in place.

First, I need to know what revision you guys are using. This appears on the loading screen and in the About box, supposing you're not using a horribly outdated version. For example:
LateralGM
v1.6.0 beta (r###)
where ### is your revision number.

Second, you will need step by step instructions on how to reproduce this problem. For example, I took the following steps in beta2, r370, and was unable to reproduce your issue:
1) Open LGM, blank/new game
2) Right click on the Objects folder, Create Resource
3) On the bottom-middle of the object's window, click the little icon that looks like a calendar. This will bring up the "Event Selector"
4) In the Event Selector, left-click on the "Collision" event
5) On the right pane, it asks for "Collision Object", with a dropdown. Click the Dropdown, and you will see two options:
<choose an object>
obj_0
6) Select the latter option (obj_0)
7) Most Important Step!!! Right Click or Double Left Click on the Collision event in the Event selector's left pane (the one we single left clicked on before). This finally adds the event to the object.
The following steps are extraneous:
8) Close/hide/move the Events Selector away so that the Object editor is visible
9) Observe that obj_0 now has a collision event, denoted with the Collision Red Arrows Icon, and labeled "obj_0". It should also be selected.

Quote from: Game_boy on June 18, 2009, 10:21:08 am

Yeah, that's a bit more serious. The majority of existing GM projects use "=" rather than "==" I think.

People who do that instantly go down on my assimilate-as-soon-as-possible list.

Then there's the Pascal syntax.
if (a = b) then begin
 b := 2;
end;

Valid GML syntax, valid Pascal syntax.

In LGM, we solved this problem with something called a WeakReference, but actually created our own called a ResourceReference. The idea is to only have 1 hard reference, so that when that reference goes away, so too does the resource (via the garbage collector in Java), but the WeakReferences remain but resolve to null. I guess this just encourages null checking everywhere.

Even if "Game Maker Language" is trademarked, you can still call it GML, because GML can be anything. It could be Gnomes Making Love, or Gnu Master License, or Gaseous Molten Lava, or Game Manipulation Logic