[SOLVED] Bug? get_physical_size() and get_mouse_pos() unexpected values with resized window.

[__ess__]

Hello!

I have an issue with resizing the game window and getting accurate values from get_physical_size and get_mouse_pos functions and I'm unsure if I'm missing something or if this is a bug. Have been reading through some of the documentation pertaining this but haven't found anything that would explain this behaviour.

I have attached a small example project where anyone can test this if they want, but below is the code in it's entirety for this test.

Code: Select all

init python:
    def show_info():
        print("physical size = {}".format(renpy.get_physical_size()[0]))
        print("mouse pos = {}".format(renpy.get_mouse_pos()[0]))

screen my_screen:
    modal True

    key "K_SPACE" action Function(show_info)

label start:
    call screen my_screen
    return

With this test, I have a project size of 1280 x 720. In the test, I have a simple screen that aims to get a function to run every time one presses the space button on the keyboard. This function prints out the width of the game window and the x position of the mouse into the debug console.
In my test, I launch the game, resize the window to be maybe around 30 - 50% smaller, then press the start button of the game menu.
I then position my mouse in a location on the x-axis inside the game window, press space, then move to another location further to the right, press space etc., always within the game window.
Then afterwards, I check the log to see what has been printed out, and I find that even though I've always stayed inside the game window, the output shows the last time I pressed space, the x position of the mouse is a larger value than the actual size of the window.

Screenshot of the console below from one of these tests:


I can't make any sense of why this happens. I'm trying to make this work in an actual project and have kind of hit a snag with the results of this. Does anyone know the reasons for this happening? Should I perhaps file this as a bug?

Thanks!

[__ess__]

Here's a gif showing the problem as well, using same code as my first post.

[m_from_space]

Well, if you have a project that's 1280 x 720 and then resize the window, the project (luckily) is still considered 1280 x 720, otherwise your images would not be part of the screen anymore if you set them at a position that is not relative to the screen and hotspots wouldn't work. I think it's working as intended.

get_mouse_pos() will always give you the position as if the player is doing it inside the intended screen, so you don't have to calculate anything. (Beware that if you check for mouse_pos and the player is not inside the window, the values are meaningless.)

[__ess__]

Well, if you have a project that's 1280 x 720 and then resize the window, the project (luckily) is still considered 1280 x 720, otherwise your images would not be part of the screen anymore if you set them at a position that is not relative to the screen and hotspots wouldn't work. I think it's working as intended.

get_mouse_pos() will always give you the position as if the player is doing it inside the intended screen, so you don't have to calculate anything. (Beware that if you check for mouse_pos and the player is not inside the window, the values are meaningless.)

Thanks for your response!
I might be a little slow this morning, so my apologies if I'm misunderstanding something.
I'm still not entirely sure I understand. get_physical_size gets the size of the game window rather than the project size, and get_mouse_pos gets the position of the mouse inside of the game. So if the window size is 1280 pixels wide, and if the mouse is flush against the left side of the game window (inside of it of course) the x coordinate shows 0. If the mouse is flush against the right side of the window, then the x coordinate shows 1280.
So if the size of the window is resized to 1060 pixels on the width, then the mouse still has an x coordinate of 0 on the left side and on the right side, it should now have a coordinate of 1060 if I'm not mistaken?

But if that is incorrect, am I understanding correctly then that the size of the actual project and its scale influences how Ren'Py calculates the position of the mouse with the get_mouse_pos function? So the mouse coordinates are not in relation the window but rather to the project, if that makes sense.

So with the example image below, the blue frame is the game window size, same as the project size, and the red frame is the resized window which has a new width.
Would this be correct?

[__ess__]

Just want to give an update to say that I adjusted my project to use the config.screen_width and config.screen_height instead to account for this behaviour to make it function as per my needs for my project. Thanks again for informing me @m_from_space. Perhaps this thread can be useful to others who may be wondering the same!

[Ocelot]

Yes, that is correct. Everything in RenPy always work as if game size is of project size, because otherwise absolute positioning would become extremely hard. There are only a few ways to break out of this and see different results. get_physical_size is one of them.