Ren'Py 6.99.12 Prereleased

[xela]

Everything I could test seems to be working

There is a small issue with the docs:

viewtopic.php?f=8&t=41429#p436073

it was a very good idea to get rid of side_image and two_window cause those are not are the only two sensible use cases and screens are super easy to extend nowadays anyway but this doc will create some confusion. It should either be deleted or state that it only works ("out of the box") in versions prior to .11.

[xela]

Everything I could test seems to be working

Ok... I spoke too soon

This results in a VERY different behavior, but I am not sure which version changed it:

Code: Select all

screen vp_test():
    viewport:
        xysize 100, 100
        has fixed
        add atl_test
        
transform atl_test():
    Solid("F00", xysize=(10, 100))
    ypos 100
    linear 1.0 ypos 0
    repeat

label start:
    call screen vp_test

in .12, you always see the whole thing. In older version(s), you just see the part within the size of the viewport! In a way, this new behavior defeats the purpose of viewport (at least partly). I am using something along these lines in a minigame but we can prolly just use limit size of a render or something along those lines if by chance this was intentional and isn't a bug.

[PyTom]

I've bumped the prerelease to 6.99.12.1956.

This fixes some issues with translating the Ren'Py launcher and the default gui.

It also works around xela's issue above. It's a somewhat weird issue, since what's happening is that a 100x100 fixed is created inside a 100x100 viewport, the viewport is noticing that nothing interesting is going on, and it's not bothering to clip - and hence showing the Solid that's outside the 100x100 fixed. Ren'Py now takes a subsurface as part of viewport drawing, which should fix this.

[xela]

Yeap, my weird code got fixed

Tnx!

[ReAnimator]

Hi,
thanks for looking into the issue!

[Donmai]

Hi. The Portuguese translation of the Launcher is now working OK (see viewtopic.php?p=430424#p430424). The only problem that persists is that Ren'Py keep showing English names for the month and day of the week.

Am I doing the translation the wrong way?

Code: Select all

    # 00action_file.rpy:26
    old "{#weekday}Saturday"
    new "{#weekday}Sábado"

    # 00action_file.rpy:47
    old "{#month}December"
    new "{#month}dezembro"

    # 00action_file.rpy:235
    old "%b %d, %H:%M"
    new "%d/%m/%Y, %H:%M"

Thank you for your hard work.

[nyaatrap]

The only problem that persists is that Ren'Py keep showing English names for the month and day of the week.

I think this is a problem I also got. I couldn't find what is an issue exactly so didn't reported yet.

[Obscura]

Sprites are positioned properly on my loaded saves now. Thank you Tom!!!

[xavimat]

Sorry for the explanation in bad English:

There is a strange behaviour in the viewport of game_menu used by the help screen (the one with "tabs" for keyboard and mouse).
The side bar for scrolling the text does not disappear when other tab, that doesn't need the bar, is shown. It disappears when the mouse passes over it.
Then, the side bar does not appear when the tab that needs it is shown again, only when the scrolling starts (so, the user does not know that there is more text below to be read).
I've made a test duplicating the content of the keyboard_help screen (so it needs the viewport to scroll it) and capturing it in video:

renpy_6_99_12.mkv.zip

(308.03 KiB) Downloaded 9 times

Spanish translation: Is working Ok, but with the same problem shown by Donmai with the Portuguese translation.

[nyaatrap]

I remember that 'disappearing scrollbars issue'. I thought this is came form my own code problem, but it looks it happens more majorly.

[nyaatrap]

Oh BTW, don't you think to hide 'roll back side' from unrelated hardwares? The first time I saw it, I though 'what the fuck this preference'. Now I know this is for touch hardwares, but still I think it's annoying to see this preference on unrelated hardwares.

[PyTom]

I don't know how to detect touchscreen hardware in a cross-platform manner. (I could turn it off on macs, though.)

[ReAnimator]

Hi,
Video playback issue is solvable or do I need to do something to adapt to the recent change on Automatic channel definition?

Edit

Okay, it's now playing by specifying channel names for the movie, previously it worked without it.

[Arowana]

While trying 6.99.12, I saw some strange behavior with dynamically cropping and then rotating an image. The strange thing is that it seemed computer-dependent.

Here's an example of an image that is dynamically cropped and rotated:

Code: Select all

image cropped:
    Transform("images/circle_untrimmed.png", crop = (0,0,146, 146))
    xpos 0.5 ypos 0.5 anchor (0.5, 0.5)
    block:
        rotate 0
        linear 1 rotate 360
        repeat

When I showed this image on one computer (a small PC, 1366x768 resolution), the circle rotated around its center as expected. When I ran the same exact code on another computer (a large macbook, 2880x1800), the circle rotated around an outer point and was also oversized.

It's not a big problem or anything; I'm just a little curious about what causes the difference. I've attached my code with image included if that helps.

[PyTom]

Question: Is the mac using high DPI mode?