Mal Graty

That traceback looks like a straight-forward Python error on your end. `600` is in integer, rather than a tuple representing a size. I'd suggest reviewing the `pygame` documentation and updating...

It may not be pretty, but this is entirely legal and functional: ```rpy label start: call a(1) call alternate_greeting(2) return label a(foo=1): "Hello [foo]" label reentry(foo=1): "I'm conversing with [foo]."...

Fair enough, I'm just always wary of lint accidentally becoming an opinionated "we don't think you want to do this" (weird label structuring) tool vs a "these are actual problems"...

> https://github.com/renpy/renpy/commit/aeb4586b5655f53b08f1e588bafdb2a8cf3cc948 - This seems wrong. If someone was to write: > ``` > position(absolute=0.5) > ``` > They'd get position with relative set to 0.5, which is very confusing....

This seems to sound like `config.window_hide_transition` and `config.window_show_transition`. https://www.renpy.org/doc/html/config.html#var-config.window_hide_transition

Behaviour as described sounds like what you might see if `call_in_new_context` was being used incorrectly.

I think you're looking for `config.raise_image_exceptions` which can be set to `False`.

I don't think this makes sense on the base input value. It seems too niche to see widespread use, while also being too simple for most cases that want to...

This isn't about facilitating the disabling of the input, that is already possible with the existing Disable action attached to the InputValue. It's about disabling the field once enter is...

I'm not saying this has no use, and that we can't do better in the realm on input management, we absolutely can, however I do feel like this feature as...