MMF2 Build 250 (BETA #2)

I don't understand very well what you mean, but if the problem you mentioned in the other thread happens when you run the frame rather than the application, then yes it's the same issue.

The "Jump to frame" action choose a frame in frame selector, followed the selected frame number when inserted or replaced frame.

Is "Jump to frame" action choose a frame in expression follow the frame number when inserted or replaced frame?

Mentioned new SWF beta is not available, should be redownload 250?

I don't think it is. You'd have to change the expression manually, since the expression would presumably be used for a variable based on something independent of frame order, as opposed to a constant (the number of the frame, as selected with the regular dialog and not the expression editor).

Quote:

---

Originally Posted by Yves

Oh, I see, it's when you use the Run Frame command. I'm not sure if we want to modify that. The problem is that in the case of a frame parameter the validity of the frame is tested in the action, while with an expression parameter the validity of the frame is tested after the frame is closed. As it's a (very) minor issue I think we won't change it.

---

This feature was a source of frustration for me when I just started out with TGF2. Of course now I think it's perfectly logical, but for the sake of newbies I think in the future there should be a warning along the lines of "You selected to run a frame, and not the whole application. Some functions work differently, like for example Jump to Frame etc etc" ... with a "Don't display this message again" or a way to turn the warning on/off in the preferences.

Can infinity scroll in the direction of the minus when "Virtual width" and "Virtual height" are set to -1?

Because the vertical scroll shooting game scrolls from the under to upper, it is not possible to infinite scroll in the current state.

That's I suggest the new feature.

A fix for the Clickteam Movement Controller bug that the angle snaps back to zero when the speed is zero would be neat. This problem makes me somehow mad at the moment :)

When creating an object (with an event) and setting its position relative to another object, the object's X Position seems to end up 1 pixel off. For example, I drag the object's position with the mouse to x = -64, y= -64. When I press the "OK" button, the event in the EventListEditor reads "Create object at -63, -64".

This seems to happen when you set the position by ONLY dragging the preview proxy/box. If you type in a value for X or Y, the bug does not occur.

mobichan