ENIGMA Development Environment

By the way, i invite you to attend to my Ph.D. defense. It will happen in M.I.T on June 2034, and the title is :

" In Java, how to insert a component in a toolbar : a 20-year study ! "

  

The error is still here. In EnigmaRunner.java, the error comes now from :

LGM.tool.add(new JToolBar.Separator(), 8);
When we want to add a component in a toolbar at a given position, it seems to accept any component except a separator ! It doesn't trigger an error if you don't specify the position :

LGM.tool.addSeparator();
But of course, we don't want to add the separator at the end of the toolbar. I don't have for the moment a solution (Except the 'useLegacyMergeSort'  ).


Update :
Java : "Write once, run anywhere" Write once, test everywhere

Hello,

I would like to implement an undo /redo function in the rooms editor. I think this is an important feature missing. I know Java and Swing so i can do it myself. What do you think ? Are you interested ?

P.S: An interesting article about how to implement correctly undo function with Swing : http://www.javaworld.com/article/2076698/core-java/add-an-undo-redo-function-to-your-java-apps-with-swing.html

Wait, look the line should be commented add that adds stopb.
LGM.tool.add(new JToolBar.Separator(), 4);

The line directly after that, is it commented out or not?

Ok the following line is commented, but i've still the error message. This afternoon i commented all lines concerning stopb, but this is easy to do :  if you do a search file with eclipse, in 30 seconds you can find and modify all lines. There must something like 10 lines to comment.

Edit :
If i remove line 169:

stopb.setVisible(false);
the error is also gone, but i find cleaner to comment all lines related to stopb.

Robert, thanks a lot for you help, but are you sure you committed correctly your modification ?
To be sure, i did a new clean install (i deleted the enigma-dev folder), and i've still the error, but it seems the code for the button is still here. If i open in the enigma.jar file the EnigmaRunner.java file, the code for the button is still here:

public JMenuItem busy, run, debug, design, compile, rebuild, stop;
public JButton stopb, runb, debugb, compileb;
stop.setVisible(false);
stopb.setVisible(false);
public void populateMenu()
{
stopb = new JButton(); //$NON-NLS-1$
stopb.addActionListener(this);
stopb.setToolTipText(Messages.getString("EnigmaRunner.MENU_STOP"));
stopb.setIcon(LGM.getIconForKey("EnigmaPlugin.STOP"));
LGM.tool.add(new JToolBar.Separator(), 4);
public void compile(final int mode)
{
if (!assertReady()) return;

stop.setEnabled(true);
stopb.setEnabled(true);
etc..

I am having trouble understanding what you are asking egofree. Are you saying you can't right click the jardescription and just build the plugin? Also, you have set the build description to link LGM's jar and everything right?

If i right click on the description.jardesc and build the jar, it says 'Can't find the manifest'. It's because it is looking for /lgmplugin/META-INF/MANIFEST.MF", but by default the project in Eclipse is Enigma not lgmplugin. It's very easy to fix : i just have to rename the folder 'Enigma' into 'lgmplugin'. I was just wondering if it was always like this.

Can you provide a simple test-case game that works in GM:Studio but fails in Enigma? I'll have a look.

Ok, i did the exactly the same with GM, and everything works as expected. This is not the case with Enigma right now.

Here is the GM project zipped :
https://dl.dropboxusercontent.com/u/29802501/TestTimeLine.gmx.zip

For downloading the Enigma project, see my previous message.

With a simple project, i did three modifications to test timelines:

1) A time line with one step at 60:

timeline_0:
step 60 -> execute script -> show_message("60");

After two seconds, it displays 60. Works the same on GM and ENIGMA.

2) I add a step at 1, which just sets a variable:

timeline_0:
step1 -> execute script -> x=1;
step 60 -> execute script -> show_message("60");

On GM, it displays correctly the message 60 after 2 seconds. With ENIGMA, it displays the message immediately.

3) I added a third step at 120, which displays another message :

timeline_0:
step1 -> execute script -> x=1;
step 60 -> execute script -> show_message("60");
step 120 -> execute script -> show_message("120");

On GM, it displays correctly the message "60" after 2 seconds, and the message "120" after another delay of 2 seconds. With Enigma, it displays immediately the message "60" and after another delay of 2 seconds it displays "60".

Update : i've found that if you restart ENIGMA and load again the project everything works as expected. To be sure i made again from scratch the project with ENIGMA and the bug happens exactly as i described earlier. You can save the project, it doesn't change anything, but you have to close and restart Enigma if yout want to 'remove' this bug. Perhaps the bug is not within ENIGMA but LateralGM ?

Update2:
A lot of strange things happen with timelines if you don't restart ENIGMA and load again the project. Another slightly different example : if you first create step 1, which displays nothing, run the application, nothing happens as expected, but if you add another step at 60 which displays a message, and run the application, nothing is displayed ! If you restart ENIGMA and load the project, everything is again ok.

In conclusion, every time you make a modification to a timeline, you need to restart ENIGMA to be sure it works as expected.