For utf8, I adapted this code from Bjoern Hoehrmann (for both coding and decoding) :
https://github.com/anael-seghezzi/Marat … tinyutf8.h

Text handling in M4 support utf8 (MGui2 too)

I did this refactoring mainly for readability, not with the intention to make code exchange impossible.
It just was not in my head that re-merging code could be desirable so I did not think about that problem.

I might actually port back some code to Maratis, seeing how some people request Android support. I worked a little with Android in the past and got one version of Neo (before the refactoring took place) to compile and run on Android. It wasn't fast, it had graphics glitches on some devices but it worked. Another point where I could help is the Lua API which could be automatically generated for better coverage and structure.

By the way: I saw you did some unicode stuff in your "development branch". What middleware do you use for that?

Have a nice day!

Cheers!

Have fun with it!

Changes include: Initial implementation of post effects and a post effects configuration dialog and multiple input improvements to prevent input lag. This version also includes an experimental crash dialog that shows a stack trace for easier bug-reporting.

This is the first daily build that is cross compiled for Windows using MingW. Please tell me if it works for you!

You can download the binaries on my website (as always ): http://scary-squid.de/wordpress/?page_id=83
Have fun!

I'm very fine, thank you for asking

I wrote the "Maratis Manager" some time ago to overcome some usability problems with the Maratis editor like opening recently accessed projects and updating the editor from SVN.

Somewhat later I decided to experiment with FLTK a little and started to integrate Maratis with it.
Well, this experiment started growing and evolved into the Neo editor you can download today.

You can find more info here: http://scary-squid.de/wordpress/

Feel free to test it

I was fooling around on my Linux machine when I stumbled upon your "Maratis Manager" application.

How are you? Tell me more about this new editor of yours!

Peace.

I changed quite a lot under the hood for better joystick support and fixed some bugs in the Lua API.
Also the drag'n'drop feature now works as expected. Only the assimp integration is missing but I don't think that it's a good idea to do that. You should convert non-native meshes manually.

You can download the development version on my website: http://scary-squid.de/wordpress/?page_id=83

Have fun!

You problems with the key input is about a timing problem between the update thread and the rendering thread. If the rendering takes too long then the update will not be called often enough for your input to get through.

I will do the drag'n'drop thingy exactly like you say. Sounds reasonable to me

For files types, as there's not much files types to be used,
maybe allow some, and display a message when it's not one of those :

maratis : MESH, LEVEL, MPROJ
text : OTF, TTF
sound : OGG, WAV, AIFF
+ those supported by assimp ?

Noticed another bug, i tried a project who got key inputs in a object oriented script,
sometimes i have to press the key more than 10 times to trigger my action,
i'm gonna do some more test before sending you the file

Akira_san: Could be implemented. The same for level files.