Skip to content

Conversation

@sixfourtwelve
Copy link

@sixfourtwelve sixfourtwelve commented Nov 17, 2025

No description provided.

for the frame wasn't taking into account
Copilot AI review requested due to automatic review settings November 17, 2025 23:18
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes a rendering issue on high-DPI (retina) screens by updating r_window_get_vsize() to use the actual framebuffer size instead of window parameters. On retina displays, the framebuffer dimensions are typically 2x the window size in screen coordinates, and this change ensures correct rendering dimensions are returned.

Key Changes:

  • Modified r_window_get_vsize() to query framebuffer size directly via glfwGetFramebufferSize() instead of reading cached window parameters
  • This ensures the function returns pixel dimensions of the actual rendering surface, which differ from window coordinates on high-DPI displays

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant