MMF2 Build #248 (BETA 6)

Hi everyone,

A new beta version of the build #248 is available (beta 6), it addresses 2 bugs reported in the previous beta version and the Java runtime now supports transitions. If no specific issue is reported in this version, it will be the official release of the build 248.

MMF2 Standard
MMF2 Developer

(ps: this is the normal version of MMF2, not the HWA version, the HWA version will be updated asap)

This version is a BETA version, you must make backup copies of your applications before loading them. We expect the final version of the build #248 to be released within a few days.

This build contains the Java runtime.

If you see any problem with this build, please report it here, thanks !

Yves.



Fixes and [color:red]new features[/color] in this version


- Edit box : scroll to end action may generate odd issues

- Any extension object with images : (dialog box object, button object, etc) images may disappear if you edit the object from the workspace window or property bar when the frame editor is not opened.

- Java runtime : frame and object transitions are now supported.




Fixes and [color:red]new features[/color] in beta 5

- Animation editor : screen flickers while dragging the hot spot/action point around.

- Animation editor : selected animation not displayed as selected the first time you click it.

- Event editor : the comment editor is now resizable.

- [color:red]Menu editor[/color] : new "Permanent shortcut" option in the properties of a menu entry. If this option is selected, the shortcut triggers the command even if the menu is hidden.

- Runtime : the End of music condition was not triggered at the end of the music after a Pause / Resume action.

- Layer object : object z-order messed up after a Sort action and a scrolling.

- BMP filter : problem with BMP files exported by some graphic tools.

- [color:red]Java[/color] : new Array object




Fixes and [color:red]new features[/color] in beta 4

- Runtime : objects with the "Visible at start" option not checked are no longer shown when they are created with a Create Object action.

- Runtime : when an active object having a fade out transition and being scaled is destroyed, the object fades out at its original unscaled size.

- Runtime : bug in new expressions that return alterable values and strings by index.

- General : crash when loading some applications with the build 248.

- Properties : Global Values are 1-based but in the Properties box of the application the first Global Value is displayed as "0 (Global Value A)".

- Expression editor : the animation number is displayed as 1-based in the expression editor although it's 0-based.

- Expression editor : the variable number in Set Alterable Value is displayed as 1-based althought it's 0-based.

- Event editor : Run Frame button disabled in behavior editor.

- Draw object : doesn't release mouse events if you quit the frame when the user clicks inside the object.

- [color:red]Timer-based movements[/color] : new property in the Frame properties. When this option is selected, the movement and animation speed of the objects in this frame is based on the exact time difference, making it independent from the machine speed. Note: for compatibility reasons, this option is not selected by default in frames of old applications. If this option is not selected, the speed is based on a frame count, less precise. A second property, Movement Timer Base, allows you to specify the value (frames per second) of the timer on which movements are based when the Timer-based Movements option is selected. It allows you to define the frame rate of the movements and animations independently from the frame rate of the application. Note: these options have no effect on the Invaders movements.

- [color:red]Movement speed[/color] : the maximum value of the speed of movements is now 250 instead of 100 (except for the Invaders movement).

- Java : known issue, the Windows controls don't work in Java applets. This issue won't be fixed in this build. They work fine in Java stand-alone mode (MMF2 Developer).

- Java : new AVI object. Note: this object requires Java Media Framework to be installed.

- Java : Layer object IsVisible condition reported always false

- Java : the object collision mask was not created from the alpha channel, resulting in a boxed collision detection.

- Java : String object, Set Text action was based on 0 instead of 1.




Fixes and [color:red]new features[/color] in beta 3

- Application corruption : sometimes MFA files could become corrupted. We have fixed a possible reason for this issue (hopefully the unique reason) and have also fixed a bug in the routine that was saving applications to a temporary file before overwriting the MFA file (on some machines it was directly overwriting the MFA file without using a temporary file). Additionnally if the autobackup feature is not enabled, MMF2 now proposes you to activate it. So theoretically nobody should get corrupted applications anymore.

Note: for applications that are already corrupted, you might get a new error message that asks you to contact us. Please do it, thanks. :)

- Random images : also we might have fixed the problem of images randomly switched in some applications. Hopefully the 2 or 3 users who have reported this issue can test this build and confirm if it's fixed or not. This problem was happening after you change the colors or frames of an active object and at least 2 instances of this object are present in the next frame.

- General : the application is no longer marked as modified when you open the global event editor, a behavior editor or some tabs of the Data Element editor.

- [color:red]Navigate toolbar[/color] : the frame index is now displayed in the frame list

- Property window : properties being edited not validated before Run Application command. This was also causing issues with image and animation properties.

- Library window : on Windows Vista, crash when trying to view 2 objects without closing the preview window (the preview window was not closed automatically).

- [color:red]Frame editor[/color] : the number of selected objects is now displayed in the status bar on the right of the mouse coordinates.

- Frame editor : objects created at an incorrect position when you drop files to the frame.

- Frame editor : objects created in the event editor and then removed from the event editor were not always removed from the frame and couldn't be deleted. They are now automatically removed from the frame when you reload the application.

- Properties / Alterable values : fix in routine that checks if a name is allowed or reserved.

- Event editor : the Select Group dialog box is now resizable.

- Event editor : cannot enter more than 4 digits in the edit boxes in the Pick object from zone dialog box.

- Event editor : top condition incorrectly selected in some cases.

- Picture editor : problem when importing some animated GIF files.

- Picture editor : sometimes in zoom mode you have to enlarge the window to edit the bottom row and the right column.

- Animation editor : "non empty" mark of animations not always updated.

- [color:red]Animation editor[/color] : new shortcut keys to crop images : SHIFT + CONTROL crops all the directions of the current animation, SHIFT + CONTROL + ALT crops all the animations of the current object.

- Stand-alone applications : sound filters are now automatically added if you use only Play Sound File actions (and no Play Sound action).

- Stand-alone applications : graphic filters are now automatically added if you use the Load Frame action of the active object.

- Installer : internal error after adding an external file and building the installer.

- [color:red]Runtime[/color] : new Get Alterable Value & String By Index functions.

- Runtime : possible random crashes in Save/Load Frame Position.

- Runtime : memory leak for objects that contain alterable strings after Save/Load Frame Position.

- Runtime : sounds sometimes swapped when you load a position from a different frame.

- Runtime : data of movement extensions not saved after Save Frame Position.

- Runtime : crash when using SET DIRECTION action in some cases with the platform movement

- Runtime : speed increase in some cases when colliding with a platform and tweaking the X and Y coordinates of the object.

- Runtime : crash when you close an application and the same sample is being played on several channels at the same time.

- Runtime : Set Layer action not working correctly for hidden objects.

- Runtime : frame collision mask not resized after Set Frame Width / Height.

- Runtime : layers without "visible at start" option not hidden after a frame restart.

- Runtime : crash when the maximum number of objects is reached and collisions between lots of objects occur at the same time.

- Runtime : "Include external files" option not compatible with embedded binary files.

- Runtime : backdrop objects are hidden one frame too late when you hide a layer.

- Button object : when you use the TAB key to give the focus to a button with a text and a picture, the picture disappears.

- Counter object : bar / set color action not working in solid color mode.

- Counter object : when a counter is set to Numbers mode the font listed under Text Options is garbled.

- Dialog Box object : Set Control Position action also resizes the controls when it's used when the dialog box is closed.

- Explorer object : tree control not correctly resized if you resize the object and the tree has a vertical scrollbar.

- [color:red]List and Combo Box objects[/color] : new "Change line" action to modify the text of a line.

- Quiz Object : fix in wrong answer dialog.

- [color:red]Special object[/color] : new "Arc tangente of y/x" expression.

- [color:red]Storyboard object[/color] : new "Frame position has just been saved" condition. This condition is true the next frame after the frame position has been saved (as a frame position is always saved at the end of frame).

- Storyboard object : conflict between the Save Frame Position and the Previous Frame / Next Frame / Jump to Frame actions.

- Sub-application object : sub-application objects created by a Create Object action or restarted by a Restart action are now immediately initialized (one frame loop is executed just after the object is created) so that you can immediately modify their global values and strings.

- SDK : cSurface::GetPixelFast was bugged in 32000/65000 color mode.

- GIF filter : fixed a transparency bug in animated GIFs.

- [color:red]Java runtime[/color] : new objects have been converted - button, edit box, file, ini, rich edit, active system box, background system box

- Java runtime : Frame background color Red and Blue value were inverted

- Java runtime : Layer is visible returned FALSE even if the layer was visible

Cool! And Fast!

Now I installed this new build, works good so far. :)



Btw. I sent you an example for the window size bug.
Have you seen the issue?

I LOVE BETA´s :) more more more :):)

Just a small detail I miss.The possibility to move action\hot spot with keyboard arrowbuttons ? Like MMF 1.5,when you already selected the action\hot spot,you could continue to adjust it with the keyboard.

mm.. I'm still getting problems with Java standalone. With previous builds Java applications didn't start with full screen. Now JAva standalone applications aren't running at all.
Using java 1.6.0_06.

Cool I'll check it out. You guys rock!

Thanks,
K

Bruto Memo. It works very well here. Could you send me your application? There must be something wrong with it in the Java runtime...
And for the full screen to work, you have to ask for a standard resolution : 320x200 / 640x480 etc. It wont work with fancy resolutions.

Quote:

---

Originally Posted by Bruto_Memo

Cool! And Fast!

---

Fast and fast. We have waited this over 6 months.

The problem I haven't seen an update for is the one that makes sub-applications corrupt all even numbered frames in an application. It's only occurred in recent MMF2 beta builds as far as I know.

animation editor - moving hotspot and actionpioint the edits arent saved in global objects, (if you re-open that the points havent changed) i switched back to 247 and it didnt happen

Quote:

---

The problem I haven't seen an update for is the one that makes sub-applications corrupt all even numbered frames in an application. It's only occurred in recent MMF2 beta builds as far as I know.

---

This problem was happening in the first beta 4 and was fixed in beta 4b, I think.

Quote:

---

animation editor - moving hotspot and actionpioint the edits arent saved in global objects, (if you re-open that the points havent changed) i switched back to 247 and it didnt happen

---

I can't reproduce it and I don't see at all what could cause this issue in the build 248. Could you confirm it and if so please describe exactly what you do? Thanks.

Things seem to be working fine on this end but I don't compile to Java with what I am working on. Not enough objects yet, but they are getting there (not a dig guys!), for my app to work. The edit box issue is fixed for sure and I have not had time to do anything with the Dialog box yet but I am sure it's fixed as stated! It's looking good guys (and gals)! Thanks for all your hard work.

Quote:

---

Originally Posted by Yves

Quote:

---

animation editor - moving hotspot and actionpioint the edits arent saved in global objects, (if you re-open that the points havent changed) i switched back to 247 and it didnt happen

---

I can't reproduce it and I don't see at all what could cause this issue in the build 248. Could you confirm it and if so please describe exactly what you do? Thanks.

---

Hi Yves

I have the same also. Not tried repeating it, but this is what I've done:

Object existing in frame 5 for example. Global is ticked.

In frame 2 for example I drag a copy from frame 5 into frame 2. I then CTRL+Drag to place duplicates.

In frame 2, I change the hotspot or action point by clicking in the image. Click OK. Open up the image again and the hotspot has not been saved, it's at it's old position. If I now click on one of the nine position buttons for the hotspot or action points, click OK then reopen it, it has saved it. So looks like positioning the hotspot with the mouse positioning is not working in this case.

It's in the game I sent to François, I can send you a copy too if you like.

Quote:

---

So looks like positioning the hotspot with the mouse positioning is not working in this case.

---

Ah OK, I see it, the problem happens with any object (global or not) when you move the hot spot with the mouse. It's due to the fix I've done, I'll fix it in the final version. Thanks to both of you!

Hi Yves;

Beta 6 doesn't found the clickteam-simple_ellipse.mvx.

I am PM you 2 java standalone game examples (alone with the mfa file) that worked on beta 5, and refuse to jump to next frame in beta 6.

Quote:

---

Originally Posted by Francois

Bruto Memo. It works very well here. Could you send me your application? There must be something wrong with it in the Java runtime...
And for the full screen to work, you have to ask for a standard resolution : 320x200 / 640x480 etc. It wont work with fancy resolutions.

---

File sent. Thanks,

Giovanni, I don't see any problem with clickteam-simple_ellipse.mvx, could you send me an example? does this happen when you run an application from MMF2, when you build a stand-alone application, a Java application?

About your other example, the problem comes from the frame fade-in transition, apparently a conversion issue with an old MMF 1.5 application, I'll take a look (you can fix it by editing the settings of the transition and selecting the same transition again).

also better note - that add backdrop/pasting an object that is rotated will only paste/add it at zero degrees regardless of its angle.

Hey Yves, I sent you an example file some days ago about the window size bug after resolution change.

Have you seen the issue?

I couldn't fix it easily, sorry, maybe later if I've an idea.

OK, nice to know that you've seen it. :)

Thanks Yves;

When I try to build a java Standalone application, MMF2 display an alert about a missing clickteam-simple_ellipse.mvx extension.

Odd, are both clickteam-simple_ellipse.mvx and clickteam-simple_ellipse.jar in your Data\Runtime folder?

Yves, I reinstalled from scratch from build 239 (plain from CD),
the .jar and .mvx are "installed", but I noticed that the .jar names has an underscore after "clickteam" in beta 6
(example; clickteam_simple_ellipse.jar instead of clickteam-simple_ellipse.jar)

I put an Active Object with a Simple Ellipse movement, and can't compile a Java Standalone because is missing the jar extension.

Ah, yes, you're right, the filenames of the Java movement extensions are wrong, sorry, I didn't see it... I'll fix it in the next version.

Update: no, the filenames are OK, there is a bug in MMF2, I'll fix it. :)