Anton Chekulaev

A nice find, thanks! Will fix it for the next version.

I believe so, since you already use `com.badlogic.gdx.utils.reflect.Field` in `AbstractLmlParser`, it should be simple like `Field#getName()`. Thanks a lot, really looking forward for this little but very useful improvement.

BTW, I just thought the same technique could be applied to `LMLAction` annotation. `ActionContainerWrapper#mapClassMethods(Class)` operates reflected `com.badlogic.gdx.utils.reflect.Method` and thus could easily extract method name.

I've never played much with code obfuscation and can only guess, but should not those runtime methods like `Field#getName()` return actual post obfuscated names?

Ah, text references to fields and methods from LML templates, right. I think it's a common practice to note if library requires any extra Proguard rules, at least, as I...

Thanks, will do! But what about `VisUI`, as of I know it is still not updated to `LibGDX 1.9.8` and should do that sometime soon. Maybe it would be better...

I can't say for sure if current *VisUI* is compatible with latest `LibGDX`, but @kotcrab is working on the new version https://github.com/kotcrab/vis-editor/issues/275

@czyzby I've had some time playing with `1.9.1.9.8-SNAPSHOT` and it seems pretty stable. I thought it's ready to go, but at the last moment I decided to make PR and...

Hi @Snehks, Thanks for the report. Sorry for the delay, but I do not actively maintain this project atm. I will check on the issue next week and hopefully prepare...

Hi, sorry for not coming back to you earlier on this one. The problem was identified a while ago and still didn't get any resolution. The issue here is with...