Repository navigation
docs: explain example sources and fix fullscreen restore failure - #20
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add purpose comments to all 30 maintained source/script/header files, extend the source map, and replace obsolete README script names with the V-native commands present at IMGUI_REVISION.
Also preserve normal restore bounds when toggling a maximized window through fullscreen. The Linux compile and portable-package jobs failed the existing shortcut test because the explicit glfw.restore_window call before entering fullscreen races the window manager's state transitions. Enter fullscreen directly while retaining the prior maximized flag; the existing exit path restores maximization. The geometry assertions are unchanged.
Validation:
Full application rebuilds, Windows behavior, Android/device tests and packaging await CI. setup.vsh still calls the removed run_demo_windows.ps1 on Windows; the README documents the available upstream run_demo.vsh route. That separate launcher defect remains maintenance follow-up.