Pascal Stücker

I've looked a bit deeper into the Windows Store Python issues. The Windows Store Python does something very odd. Rather than adding the python install folder to the PATH, `%localappdata%/Microsoft/WindowsApps`...

It doesn't really matter too much whether this is a single PR with many commits or many PRs with many commits. As the changes are very localized (one isolated change...

There really isn't a great way to do large scale PRs via Github. You'd need to create a PR for each commit for us to approve & merge individually. Doesn't...

Wouldn't it be more advisable to fix the source of the damage, rather than applying a workaround?

I think the cleaner way is to add a generic translation resource, which accepts standard `.po` files via exports and then offers a translation service back. That way it'd also...

I think that offset was chosen back when we moved to Github, to ensure that we get properly incrementing build revisions.

Yeah, resolving those conflicts might be painful. On a related note: I've been looking at in the past was to use some custom DSL tooling to automate manually writing these...

This is fairly easy to implement in Lua directly (in fact I did so a long time ago). Also we'd need to implement some form of tooling to create GTA...

I'd prefer some form of default order (alphabetically?). Otherwise one might rely on the resource working on Windows only to run into weird errors when using a Linux server later....

The underlying issue is that by accessing any property of an element, you call an implicit enew. https://github.com/sbx320/lua_utils/blob/master/classlib.lua#L309 Therefore with your enew after :spawn there's an additional onElementDestroy handler attached...