-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document use of --no-window
option for command line and vscode plugin
#360
Comments
I could not find a way to auto-detect that Godot is running in headless or "no window" mode. An option should be added that will override settings and take other actions to make running without a window more user friendly.
|
Thanks much for GUT - it's been a good experience to start working with it today! Apologies for the large comment here - I was hoping to turn this into a PR, but couldn't find a way to make it work, so here's my notes instead. I was curious about enabling One thing is that It looks like I couldn't find anything like this available in gdscript, expect for I thought maybe The Godot OS class itself does not expose anything directly helpful, despite the OS singleton in godot's source maintaining a I tried a few different things in a script: #!/usr/bin/env -S godot -s --no-window
extends SceneTree
func _init():
print("os can draw: ", OS.can_draw())
print("os props: ", OS.get_property_list())
# for p in OS.get_property_list():
# print(p.name)
# print(" " + p.name + ": ", OS.get(p.name))
print("window position: ", OS.get_window_position())
print("no window: ", OS.get_window_position() == Vector2.ZERO)
# print("minimized: ", OS.window_minimized)
quit() One hacky option is something like: It seems there's no way to opt-in to |
Do you want to talk about it there https://github.com/bitwes/gut-extension#gut-extensionadditionaloptions in Possible Uses ? Like
I tested it, it works :) ! |
Per #357, you can use the
--no-window
Godot command line option to hide the Godot window when running tests. You can also add this option to the "Additional Options" in the VSCode GUT Extension. This should be documented somewhere so it's easier to find by others. There are also some considerations to make when using it.pause_before_teardown
will cause the tests to hang since you won't be able to see the screen to click "continue". Again, if the option is detectable GUT can take the right action here.The text was updated successfully, but these errors were encountered: