ENIGMA Development Environment

Also, I was looking through the code, and I saw that we do have a RoomEefWriter/Reader (as an alternative to the RoomGmDataWriter/Reader), it's just not hooked in because it was experimantal. Again, the intent is to eventually switch to something like that, so if you want, go ahead and thoroughly review that code to make sure it doesn't have any logic errors, and feel free to switch over to it and try it out.

Yes, i saw these files, and i was wondering what was the use. Sorry but i don't intend to try them now. I am sure that it would need a lot of testing. I spent already a lot of time on the new properties and my goal is to finish this task correctly as soon as possible. (At first i thought also that it would need only a few days, but as usual in programming, there is almost never easy tasks   ) So i hope my quick fix is still ok. Of course if someone would like to propose and IMPLEMENT a new and better solution, i am open.   

How about a crazier idea and splitting the format in two, since nobody seems to think LGM deserves incremental version numbers 

As we are speaking of adding only a few variables, it seems to me a little bit overkill ! 

I propose this : let's add a 'version.txt' file inside the egm file, which will contain the version number. (An Egm file is a zipped archive). When reading the file we would test the version number :

for (int j = 0; j < noinstances; j++)
  {
  Instance inst = rm.addInstance();
  inst.setPosition(new Point(in.read4(),in.read4()));
 
  // Read new properties
  if (version ==1.1)
    inst.setScale(new Point2D.Double(in.readD(),in.readD()));
           .....

I know it seems perhaps a 'quick and dirty' solution, but we are speaking only about adding a few variables and to my knowledge we rarely have to change the data structure. If one day we would have to change a lot of things, a whole new class could be added to read the new version. Another solution would be to change the structure of the egm format, and add for example metada, but as egm format has been made to be as quick as possible, i don't think it would fit the bill. (c.f http://enigma-dev.org/docs/Wiki/EGM)
For writing, i propose not to test the version. This means we would have always the new properties and the user should always use the latest version of Enigma/LateralGm. But as we have speaking of a free and open-source software, this should not be a problem. And again, we are not changing often the data structure.

I've finished the work on LateralGM and the modifications for the new properties are now in the repository : https://github.com/IsmAvatar/LateralGM/pull/138

In order to integrate the new properties in Enigma, the following tasks must be finished in the LateralGm plugin :  changing the new instance's properties (image_xscale,image_yscale,image_alpha,image_angle) in the new property : pre_creation_code. Also these properties must be supported when reading and writing egm files. But anyway i consider the work to be finished in LateralGM, and there is not much remaining work to be finished. About 90% of the work is already done.

I'm selling my music on the GameMaker Marketplace now, since I'm too scared to do it anywhere else, I feel like such an amateur musician.

https://marketplace.yoyogames.com/assets/525/tkg-horror-music-album-1

In the description of the song, it is written : 'Age rating: 4+'. I am not sure that a 'horror music album' is suited for a child of 4 years old ! 

I suppose that is pretty unintuitive. Did you just want it renamed to GMX, or did you have something else in mind?

I think the user should see only the possible versions for the current format, or at least the others options should be disabled.

If you open a gmk file, and you want to save the project as a gmx file, you've to specify on the right panel version '1200', otherwise it will never save the project as a gmx file but as a gmk file. This is not user friendly. I think we should change this behavior.

I've found the real problem : in order to do my tests, i was using the site http://www.binaryhexconverter.com/decimal-to-binary-converter, to convert decimals to binaries. By default they are displaying signed binaries, but i need to display unsigned decimal ! (c.f http://www.binaryconvert.com/convert_unsigned_int.html). 

I did new tests today with version 1.3.1386, and it seems now that the color values are saved in ARGB values !    GM Studio had a new release several days ago and i think they changed the way they save color values. (Or i was not correctly testing before ? I doubt it). This is good news. But it means also that with older versions of GM studio we could have problems, but it doesn't seem to me a big issue : GM Studio has an automatic updating process, and everybody should have the latest version.