philat wrote:Well, because conditional statements are renpy statements and not ATL statements...? Which seems pretty clear from the examples in the conditional statement doc and the ATL doc...?
No, it's code... I expect it to function as code, within renpy, wherever it exists, as code. In a statement, in a conditional, in a choice, in other blocks of code...
Ren'Py Script Statements
ATL Code can be included as part of three Ren'Py script statements.
https://www.renpy.org/doc/html/atl.html
Image Statement With ATL Block
The second way to use ATL is as part of an image statement with ATL block. This binds an image name to the given transform. As there's no way to supply parameters to this transform, it's only useful if the transform defines an animation. The syntax for an image statement with ATL block is:
I am not "supplying parameters to it"...
I am using it to "define an animation"...
Which, naturally would include "code" to "define the animation"... Such as sequences, flow, direction, interactions, times, delays.
This is a fourth set of "pseudo-code" that isn't apparently code. One with real specific things that can be listed, and work within it, which are easily confused with the actual "code/script", designated as "working within blocks", which describe themselves as code-blocks.
This is why I get confused... So, where does the actual code have to go, if it can't be used in these code-blocks that don't accept some code, but accept some code, just not the code I want to use, which is renpy code?
So, essentially, I have to build my own functions that do exactly like ATL, using ATL, to get renpy's code to work, with ATL, doing what it should do within ATL code-blocks, which is a whole other language, that uses renpy-like language but not renpy code, to function. Gotcha... I can deal with that, now that I realize it isn't renpy code and doesn't allow renpy code inside of those blocks, only that other set of code/script. Which looks exactly like renpy code/script, but isn't.
It saves me time... That's all that matters... and it runs smoother than what I had, even if I have to code each frame individually.
Still looking for a way to automate this, so it is, well, useful as code, or as a function.