https://github.com/chamons/ggez_render_squash
Example of ggez "squashing" when using set_screen_coordinates
https://github.com/chamons/ggez_render_squash
Last synced: 3 months ago
JSON representation
Example of ggez "squashing" when using set_screen_coordinates
- Host: GitHub
- URL: https://github.com/chamons/ggez_render_squash
- Owner: chamons
- Created: 2022-09-24T14:42:04.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2022-09-24T15:14:08.000Z (over 3 years ago)
- Last Synced: 2025-03-13T19:16:28.259Z (10 months ago)
- Language: Rust
- Size: 4.71 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Solution
I'm leaving this up in case anyone else runs into it, but it appears that ggez or one of it's dependencies is including the title bar in the window resolution. So when you request 800x600 you don't get a window with that much usable space.
This means when you call `set_screen_coordinates` you get squashed since you "lose" the titlebar space, which is only in one axis.
Some variant of this appears to fix it for me:
```
canvas.set_screen_coordinates(graphics::Rect::new(
15.5,
15.5,
ctx.gfx.window().inner_size().width as f32 / scale as f32,
ctx.gfx.window().inner_size().height as f32 / scale as f32,
));
```
# Problem
When I set set_screen_coordinates to the same resolution as my window, I go from:
to:
# How to reproduce
- Have a mac it seems (does not reproduce on my Windows box)
- Sync repository
- Set cargo.toml to a local copy of ggez to a recent devel branch 41d9abe
- cargo run
- Hit F1 to flip between the two modes