ENIGMA Development Environment

BTW version 1.4 early builds are out.......
and by this time next year people will long have forgotten 1.2, 1.3, 1.4 and moved on to 2.0. 

You made a typo :

BTW version 1.4 early builds are out.......
and by this time next year people will long have forgotten 1.2, 1.3, 1.4 and moved on to ENIGMA 2.0. 

We should maybe show it via pop-up or something that GL1 shaders don't work on GL3, GL3 shaders don't work on GL1 and GL shaders in general don't work on DX. Otherwise people will start posting "bug reports" like ego here.

I don't know how shaders work, so perhaps what i will propose is nonsense, but for the functions which set the shaders, instead what about having two different functions for each shader version, or a parameter in the function which specify the shader version ?

Looks nice Robert. I tested your example, and here is the result :

On DirectX 9, i've the following error message :

  Event[8]:   Parsing 1 sub-events:
Check `obj_terrain::draw...Syntax error in object `obj_terrain', Draw event:0:
Line 1, position 12 (absolute 11): Unknown function or script `shader_set'

With OpengGl3:



With, OpenGl1, it's ok, except a few glitches with the rivers :



It was tested on a laptop with Windows 8.1 64 bits and Intel HD Graphics 4000.

When a view is selected on the left tree, it is now displayed in the center of the window. So if you have a big room, you don't have to scroll all the room to find the view. I decided also to automatically displayed the first view in the center of the window when the view tab is selected. As there is only a few number of views and usually the first one is the most important, it makes sense to me.

I've added two features in the rooms editor, and they are now available for everyone in the latest executable of the 'Download' section. So if some people want to test these features, they are welcome.

The first is the undo :

The undo is available when the user, with the mouse or with text fields, adds, deletes and moves an object or a tile. The undo does not take into account others properties, like 'instance creation code'. If you modify these properties, you will get only the latest version when using the undo. The undo and redo can be used also with the shortcut keys : ctrl-z for undo and ctrl-y for redo. The limit of the undo history is 100. If a sprite, a background or an object is modified in the left tree, the undo is reset.

I will add settings for the undo in a future release. It will be possible to disable the undo or to change the limit of the undo history.

I've added also a preview of views in the rooms editor, with a black and white boxes. I will add also others features for the preview in a future release. For example, the preview will take into account the 'Object following' option, and it will be possible to use a filled rectangle instead of outlines.

BTW you deserve credit ..

Is it all worth it? : 

Our revels now are ended. These our actors,
As I foretold you, were all spirits and
Are melted into air, into thin air:
And, like the baseless fabric of this vision,
The cloud-capp'd towers, the gorgeous palaces,
The solemn temples, the great globe itself,
Ye all which it inherit, shall dissolve
And, like this insubstantial pageant faded,
Leave not a rack behind. We are such stuff
As dreams are made on, and our little life
Is rounded with a sleep.

1) Faster loading times

I've seen that when a project is loaded, there is a lot of events which are fired and i am not sure they are all needed at this time. For example, the updated event in the ResNode is fired each time a resource is added. I wonder if some optimization could be done on this (for example disabling some listeners when loading the project or adding them when the project is loaded) and could help the loading time.