XLua, MMF2 Extension

well i do have a somewhat ugly but probably usable backup plan for object collisions if you can't get the functions to work

Updated the distribution.

By request of a click user, I added the expression-based Lua function calls.

The error and print handling have also been changed for improved safety. All error and print events will now be queued until the end of the event loop, and then reported. This may have a small impact on the behavior of your programs. This will prevent crashes that stem from an expression being interrupted by a triggered event execution.

Fixed a bug in loading the package library, which would cause applications to immediately quit.

Some major additions to the MMF Interface. First a bunch of convenience functions that would be useful for a level editor (cough):

mmf.Frame.GetHeight
mmf.Frame.GetVHeight
mmf.Frame.GetVWidth
mmf.Frame.GetWidth
mmf.Frame.GetXLeft
mmf.Frame.GetXRight
mmf.Frame.GetYBottom
mmf.Frame.GetYTop

mmf.Mouse.GetClientX
mmf.Mouse.GetClientY
mmf.Mouse.GetX
mmf.Mouse.GetY

mmf.Object.GetFixed
mmf.Object.GetName

mmf.Window.GetCHeight
mmf.Window.GetCWidth
mmf.Window.GetHeight
mmf.Window.GetWidth

Second, I've defined the callback interface function mmf.ExportCallback.

This is undefined out of the box, but if you do define it, it will get executed every time you export an object, and the ID will be passed as the only parameter.

http://hocuspocus.taloncrossing.com/rii/xlua-dist.zip

I can't even get it to do simple function calling

D:

Try downloading it again.

Basically what you found is a corner case, an off-by-one error that I didn't expect because I never call MMF functions as the first item on the call stack (by executing an MMF function from a dofile or dostring, rather than a lua call).

Brilliant, thanks!

Time to replace lua+ with xlua... :(

http://hocuspocus.taloncrossing.com/rii/xlua-dist.zip

This release fixes a potential lua stack overflow (horrible game-crashing bugs). Actually, if you called lots of functions between other actions you'd probably never see it, but maybe you would. Random bugs suck like that, so you'd better download this!

so have you figured out edittime object properties yet

it would be nice if you could have a script stored within the extension itself, instead of having to use a string object or something (mainly if you just wanted to use xlua as a widget-type thing for something)

I had to learn them for the Dynamic Grid object, so I guess I could add something.

New release: http://hocuspocus.taloncrossing.com/rii/xlua-dist.zip

This fixes a small bug related related to MB's function bug earlier.

This also formally introduces some previously undocumented functionality. First, a few MMFI functions:

mmf.Mouse.ButtonUp(button)*
mmf.Mouse.ButtonDown(button)*
mmf.Window.GetFrameWidth()
mmf.Window.GetFrameHeight()

* These functions test current state. If you want to capture the the Button Up / Button Down events themselves, refer to the WIN Interface below.

Second, the WIN Interface:

This interface consists of a single function, win.ExportMessage(msgid, function), which allows you to bind a windows message to a lua function. When the windows message is fired (like WM_KEYDOWN), the associated lua function will be executed with that message's parameters. Here is an example that I use in Tile Lattice:

These two messages fire when an application or context menu is opened and closed. I keep the menu state in a convenient variable, so that when a user opens the application menu, the mouse clicking will not accidentally interfere with the rest of the application. Similar messages can be used to capture mouse or keyboard events, when windows are moved and resized, etc. Refer to MSDN for more documentation on windows messages.

Obviously if you're running user-defined code, you should protect or nil out the interface for security reasons.

wtf rii you're making an extension have awesome features

that has to be breaking some kind of rule

It must be illegal

Also executing an MMF function while interceping a message may produce undefined results, because the message may fire during an interval where event processing is undefined.

This post has been edited by Retriever II on Mar 14 2009, 12:58 AM

I have an instant crash in MS because of the xLua object. I'm not sure what triggers it, and isolating it will take a while. Just wanted to let you know.

Is this from the latest build or one from a couple days ago?

latest

would you be able to add a return value to the four move interface functions (MoveToFront, MoveToBack, MoveAbove, and MoveBelow), so they return the new Z-index of the object?

There's some new actions in the build now for resetting state, as a workaround for destroying the object which seems to be unstable at the moment.

There's a crash with the new reset state action. If you could come on msn and tell me the function to view the break info, then that'd be great as I forgot it :(

edit: there's also a crash with tables

This post has been edited by MechaBowser on Mar 16 2009, 02:20 PM

Until I manage to catch you on MSN, the best thing you can do, if possible, is isolate the problem to an MFA file that you can give me. Every time I change the code, I can't debug precompiled exes.