[Keyboard and Mouse Events]

I can add an onrelease mechanic to this tomorrow as I'm on my phone right now and typing code is difficult on this. It's not too hard just an extra variable for the loop on each key.

[GameStates with CStateManager]

SplashScreen is an instance of CState not a new derivative class, I know semi colons aren't needed just a habit that I don't see the need in breaking.

 

I try to make these modules self contained, so any errors are reported to the user instead of crashing the game, CStateManager checks if a CState is being pushed onto the stack, if it's not a CState it isn't allowed. The inheritance in my class module is used to have base classes with inherited values, whereas the SplashScreen in this example is just a class instance with modified public methods ( I know they're all public being Lua since we can't privatize them without a workaround with the standard class metatable )

 

It would still work extending instead of instancing but most states will not be even remotely similar so inheriting values we won't use wouldn't be wise.

[Lua Classes Module]

You could replace all _G mentions with a local table, although that would be quite messy and not make much sense?

 

If you could explain to me what it is you're trying to do with it I might be able to come up with a neater solution.

[Lua Classes Module]

Passing them as a string is needed as it manually grabs the class from the global environment. It doesn't need to be that way but I did it for uniformity because the class () function does require string names and theres no getting around that.

[More GUI work]

Yeah you should release your integration, I'd buy.

I have thought about it, i would have to write up an extensive usage guide as some elements do have their quirks which can make usage difficult, it doesn't use the flowgraph either you make elements purely with lua.